Bug#948041: impossible to update libbpf without updating the kernel
On Sat, Jan 18, 2020 at 7:48 AM Bastian Blank wrote: > > On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote: > > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote: > > > I agree --- if upstream development were happening in > > > https://github.com/libbpf/libbpf then this would be a no-brainer. It > > > appears to instead be a mirror of the source that's in the kernel > > > repo, though. > > That will be difficult as all of them are dependent on the ftrace hooks > > that are in the kernel. > > What will be difficult? > > > > > Why should we switch from kernel sources to GH is a frequently asked > > > > question so the reason was explained in libbpf README [1]. > > Let's go through it one by one. > > "Consistent versioning across distributions." > > Maybe, but the kernel is also versioned consistently. Libbpf releases are only loosely synchronized with kernel releases, and it's only due to current convention we established within community. There is nothing preventing multiple releases of libbpf between two releases of kernel. So having Linux distributions use Github's release tags ensures that all of them are building from exactly the same source code version. > "No ties to any specific kernel, transparent handling of older kernels." > > What? Either they are upstream for it or patch the source. But this > point means it can't be a direct mirror. So what is it? It is mostly a direct mirror, with some extra Github-specific stuff beside (like Travis CI testing, etc). All the libbpf source code fixes do go through bpf-next tree, though. But the point here was that libbpf itself is not built with any particular kernel version in mind. It is by design possible to use the very latest libbpf against a pretty old kernel version and this will work: libbpf will degrade some of the features (e.g, BTF type info associations), but everything will keep working otherwise (unless user requests feature that requires latest kernel version, of course: in that case BPF program will fail to load and libbpf will return corresponding error code). > > "Continuous integration testing via TravisCI." > "Static code analysis via LGTM and Coverity." > > Both are not restricted to this repo. Not sure what you mean by this. We can't have Travis CI integration w/ bpf-next source tree. But we can and we have it for Github mirror, which runs tests and static analysis for every sync pull request. We already have and are enhancing at the moment our testing set up to test multiple kernels in multiple environments. > > > > If I'm reading that correctly, the intent appears to be that it would > > > allow faster libbpf upgrades. > > Yes, one of my intent. Faster and independent. > > And how does it do that, without being upstream of the source? > > Sorry, but I intend to end this discussion here. > > Bastian > > -- > It would be illogical to assume that all conditions remain stable. > -- Spock, "The Enterprise Incident", stardate 5027.3 > > -- > To unsubscribe, send mail to 948041-unsubscr...@bugs.debian.org.
Bug#949272: marked as done (linux: The task_struct structure is defined on multiples variables.)
Your message dated Mon, 20 Jan 2020 00:43:53 + with message-id <5db214a02425623bc5dc8dcaa655a92b0b56fcfc.ca...@decadent.org.uk> and subject line Re: Bug#949272: linux: The task_struct structure is defined on multiples variables. has caused the Debian Bug report #949272, regarding linux: The task_struct structure is defined on multiples variables. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 949272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Severity: normal Hi the task_structure is defined on : ksoftirqd file kernel/softirq.c current file arch/x86/include/asm/current.h curr->rq on rq structure and others When you need to ensure as task is running need to read alls these variable and is fortune if task is running , fortune when this variables is actualised correct, on conclusion bib, big mistake. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.6+ (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Not a bug. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#949256: linux-image-5.4.0-2-amd64: zram-tools blocks shutdown (regression since 5.2)
Hi Nick, Nick Shaforostoff writes: > Package: src:linux > Version: 5.4.8-1 [snip] > either removing zram-tools package or using linux-image-5.2.0-3-amd64 @ > 5.2.17-1 > which I had before the dist-upgrade makes the problem go away. > > Since 5.4 changelog mentions zram, I suspect that it was the kernel > that introduced this regression. > If checking if the regression was introduced in a version earlier than 5.4.8-1 sounds interesting or fun, or if you'd like to test your hypothesis, then packages from the following may be useful for coarse-grained bisecting: https://snapshot.debian.org/package/linux/ I'd start here: https://snapshot.debian.org/package/linux/5.3.15-1/ Cheers, Nicholas signature.asc Description: PGP signature
irq 31: nobody cared / Disabling IRQ #31
Hi again, journalctl displays the following entries: janv. 19 23:24:53 kernel: irq 31: nobody cared (try booting with the "irqpoll" option) janv. 19 23:24:53 kernel: CPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.4.0-0.bpo.2-amd64 #1 Debian 5.4.8-1~bpo10+1 janv. 19 23:24:53 kernel: Workqueue: events_long ucsi_init [typec_ucsi] janv. 19 23:24:53 kernel: Call Trace: janv. 19 23:24:53 kernel: janv. 19 23:24:53 kernel: dump_stack+0x66/0x90 janv. 19 23:24:53 kernel: __report_bad_irq+0x3a/0xb4 janv. 19 23:24:53 kernel: note_interrupt.cold.10+0xa/0x64 janv. 19 23:24:53 kernel: handle_irq_event_percpu+0x6d/0x80 janv. 19 23:24:53 kernel: handle_irq_event+0x3c/0x5c janv. 19 23:24:53 kernel: handle_fasteoi_irq+0xa3/0x160 janv. 19 23:24:53 kernel: do_IRQ+0x51/0xe0 janv. 19 23:24:53 kernel: common_interrupt+0xf/0xf janv. 19 23:24:53 kernel: janv. 19 23:24:53 kernel: RIP: 0010:acpi_ex_system_memory_space_handler+0x149/0x1a9 janv. 19 23:24:53 kernel: Code: 5e 18 45 85 ed 74 0d 41 ff cd 41 bd 01 10 00 00 75 6a eb 33 49 c7 07 00 00 00 00 83 fd 10 74 1b 77 0a 83 fd 08 75 52 0f b6 03 16 83 fd 20 74 0f 83 fd 40 75 43 48 8b 03 eb 07 0f b7 03 eb 02 janv. 19 23:24:53 kernel: RSP: 0018:a6a1000b7910 EFLAGS: 0246 ORIG_RAX: ffd8 janv. 19 23:24:53 kernel: RAX: RBX: a6a1002d9021 RCX: 8b6144376958 janv. 19 23:24:53 kernel: RDX: 4fb15038 RSI: 0034 RDI: janv. 19 23:24:53 kernel: RBP: 0008 R08: R09: 8b614445ed80 janv. 19 23:24:53 kernel: R10: 8b614db69240 R11: 005f R12: 8b614e437d38 janv. 19 23:24:53 kernel: R13: R14: 8b614445ed80 R15: 8b6144376958 janv. 19 23:24:53 kernel: ? acpi_ex_prep_field_value+0x265/0x265 janv. 19 23:24:53 kernel: acpi_ev_address_space_dispatch+0x1f2/0x274 janv. 19 23:24:53 kernel: acpi_ex_access_region+0x1d7/0x254 janv. 19 23:24:53 kernel: acpi_ex_field_datum_io+0x107/0x194 janv. 19 23:24:53 kernel: ? down_timeout+0x31/0x50 janv. 19 23:24:53 kernel: acpi_ex_extract_from_field+0x98/0x25c janv. 19 23:24:53 kernel: ? acpi_ex_system_wait_mutex+0x19/0x48 janv. 19 23:24:53 kernel: acpi_ex_read_data_from_field+0x119/0x15c janv. 19 23:24:53 kernel: acpi_ex_resolve_node_to_value+0x1f6/0x296 janv. 19 23:24:53 kernel: acpi_ex_resolve_to_value+0x23d/0x25d janv. 19 23:24:53 kernel: acpi_ds_evaluate_name_path+0x87/0x113 janv. 19 23:24:53 kernel: acpi_ds_exec_end_op+0x90/0x401 janv. 19 23:24:53 kernel: acpi_ps_parse_loop+0x492/0x5c6 janv. 19 23:24:53 kernel: acpi_ps_parse_aml+0x91/0x2b8 janv. 19 23:24:53 kernel: acpi_ps_execute_method+0x15d/0x191 janv. 19 23:24:53 kernel: acpi_ns_evaluate+0x1c1/0x24e janv. 19 23:24:53 kernel: acpi_evaluate_object+0x137/0x240 janv. 19 23:24:53 kernel: acpi_evaluate_dsm+0xab/0x110 janv. 19 23:24:53 kernel: ucsi_acpi_dsm+0x52/0x70 [ucsi_acpi] janv. 19 23:24:53 kernel: ucsi_command+0x2c/0xa0 [typec_ucsi] janv. 19 23:24:53 kernel: ucsi_run_command+0x32/0x210 [typec_ucsi] janv. 19 23:24:53 kernel: ? klist_add_tail+0x3b/0x70 janv. 19 23:24:53 kernel: ucsi_register_altmodes+0x9d/0x350 [typec_ucsi] janv. 19 23:24:53 kernel: ucsi_init+0x2b3/0x560 [typec_ucsi] janv. 19 23:24:53 kernel: process_one_work+0x1a7/0x360 janv. 19 23:24:53 kernel: worker_thread+0x30/0x390 janv. 19 23:24:53 kernel: ? create_worker+0x1a0/0x1a0 janv. 19 23:24:53 kernel: kthread+0x112/0x130 janv. 19 23:24:53 kernel: ? kthread_park+0x80/0x80 janv. 19 23:24:53 kernel: ret_from_fork+0x1f/0x40 janv. 19 23:24:53 kernel: handlers: janv. 19 23:24:53 kernel: [] tis_int_handler [tpm_tis_core] janv. 19 23:24:53 kernel: Disabling IRQ #31 journalctl -kxb -p 2 --no-hostname janv. 19 23:24:53 kernel: Disabling IRQ #31 journalctl -kxb -p 3 --no-hostname janv. 19 23:24:53 kernel: irq 31: nobody cared (try booting with the "irqpoll" option) janv. 19 23:24:53 kernel: handlers: janv. 19 23:24:53 kernel: [ ] tis_int_handler [tpm_tis_core] janv. 19 23:24:53 kernel: Disabling IRQ #31 cat /proc/interrupts | grep 31 31: 10 0 0 0 IR-IO-APIC 31-fasteoi tpm0 Some people are complaining on the Internet but there is no explanation about this. A priori, deactivating TPM could do the trick but I'm not sure it's a good idea... Any thought about it please? :) Thank you & Best regards l0f4r0
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled"
Hi, 5 janv. 2020 à 18:59 de l0f...@tuta.io: > Multiple times per hour (despite no notable CPU-consuming activity), I get > something like the following journalctl crit/2 entry: > > kernel: CPUX: Package temperature above threshold, cpu clock throttled (total > events = Y) > where X=[0-7] (I have a quad-core i7 with hyperthreading activated) and Y is > generally a 4-digit number. > I've just upgraded my kernel 4.19.0-6-amd64 to backports longterm 5.4.0-0.bpo.2-amd64 because I had issues with light-docker. The aforementioned journalctl entries have been reassigned from crit/2 to warning/4! Maybe it's not so serious? ^^ Best regards, l0f4r0
linux-signed-i386_5.4.13+1_source.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 19 Jan 2020 10:22:58 +0100 Source: linux-signed-i386 Binary: kernel-image-5.4.0-3-686-di nic-modules-5.4.0-3-686-di nic-wireless-modules-5.4.0-3-686-di nic-shared-modules-5.4.0-3-686-di serial-modules-5.4.0-3-686-di usb-serial-modules-5.4.0-3-686-di ppp-modules-5.4.0-3-686-di pata-modules-5.4.0-3-686-di cdrom-core-modules-5.4.0-3-686-di firewire-core-modules-5.4.0-3-686-di scsi-core-modules-5.4.0-3-686-di scsi-modules-5.4.0-3-686-di scsi-nic-modules-5.4.0-3-686-di loop-modules-5.4.0-3-686-di btrfs-modules-5.4.0-3-686-di ext4-modules-5.4.0-3-686-di isofs-modules-5.4.0-3-686-di jfs-modules-5.4.0-3-686-di xfs-modules-5.4.0-3-686-di fat-modules-5.4.0-3-686-di md-modules-5.4.0-3-686-di multipath-modules-5.4.0-3-686-di usb-modules-5.4.0-3-686-di usb-storage-modules-5.4.0-3-686-di pcmcia-storage-modules-5.4.0-3-686-di fb-modules-5.4.0-3-686-di input-modules-5.4.0-3-686-di event-modules-5.4.0-3-686-di mouse-modules-5.4.0-3-686-di nic-pcmcia-modules-5.4.0-3-686-di pcmcia-modules-5.4.0-3-686-di nic-usb-modules-5.4.0-3-686-di sata-modules-5.4.0-3-686-di acpi-modules-5.4.0-3-686-di i2c-modules-5.4.0-3-686-di crc-modules-5.4.0-3-686-di crypto-modules-5.4.0-3-686-di crypto-dm-modules-5.4.0-3-686-di efi-modules-5.4.0-3-686-di ata-modules-5.4.0-3-686-di mmc-core-modules-5.4.0-3-686-di mmc-modules-5.4.0-3-686-di nbd-modules-5.4.0-3-686-di squashfs-modules-5.4.0-3-686-di speakup-modules-5.4.0-3-686-di uinput-modules-5.4.0-3-686-di sound-modules-5.4.0-3-686-di compress-modules-5.4.0-3-686-di udf-modules-5.4.0-3-686-di fuse-modules-5.4.0-3-686-di mtd-core-modules-5.4.0-3-686-di rfkill-modules-5.4.0-3-686-di kernel-image-5.4.0-3-686-pae-di nic-modules-5.4.0-3-686-pae-di nic-wireless-modules-5.4.0-3-686-pae-di nic-shared-modules-5.4.0-3-686-pae-di serial-modules-5.4.0-3-686-pae-di usb-serial-modules-5.4.0-3-686-pae-di ppp-modules-5.4.0-3-686-pae-di pata-modules-5.4.0-3-686-pae-di cdrom-core-modules-5.4.0-3-686-pae-di firewire-core-modules-5.4.0-3-686-pae-di scsi-core-modules-5.4.0-3-686-pae-di scsi-modules-5.4.0-3-686-pae-di scsi-nic-modules-5.4.0-3-686-pae-di loop-modules-5.4.0-3-686-pae-di btrfs-modules-5.4.0-3-686-pae-di ext4-modules-5.4.0-3-686-pae-di isofs-modules-5.4.0-3-686-pae-di jfs-modules-5.4.0-3-686-pae-di xfs-modules-5.4.0-3-686-pae-di fat-modules-5.4.0-3-686-pae-di md-modules-5.4.0-3-686-pae-di multipath-modules-5.4.0-3-686-pae-di usb-modules-5.4.0-3-686-pae-di usb-storage-modules-5.4.0-3-686-pae-di pcmcia-storage-modules-5.4.0-3-686-pae-di fb-modules-5.4.0-3-686-pae-di input-modules-5.4.0-3-686-pae-di event-modules-5.4.0-3-686-pae-di mouse-modules-5.4.0-3-686-pae-di nic-pcmcia-modules-5.4.0-3-686-pae-di pcmcia-modules-5.4.0-3-686-pae-di nic-usb-modules-5.4.0-3-686-pae-di sata-modules-5.4.0-3-686-pae-di acpi-modules-5.4.0-3-686-pae-di i2c-modules-5.4.0-3-686-pae-di crc-modules-5.4.0-3-686-pae-di crypto-modules-5.4.0-3-686-pae-di crypto-dm-modules-5.4.0-3-686-pae-di efi-modules-5.4.0-3-686-pae-di ata-modules-5.4.0-3-686-pae-di mmc-core-modules-5.4.0-3-686-pae-di mmc-modules-5.4.0-3-686-pae-di nbd-modules-5.4.0-3-686-pae-di squashfs-modules-5.4.0-3-686-pae-di speakup-modules-5.4.0-3-686-pae-di uinput-modules-5.4.0-3-686-pae-di sound-modules-5.4.0-3-686-pae-di compress-modules-5.4.0-3-686-pae-di udf-modules-5.4.0-3-686-pae-di fuse-modules-5.4.0-3-686-pae-di mtd-core-modules-5.4.0-3-686-pae-di rfkill-modules-5.4.0-3-686-pae-di linux-image-5.4.0-3-686 linux-image-686 linux-image-5.4.0-3-686-pae linux-image-686-pae linux-image-5.4.0-3-rt-686-pae linux-image-rt-686-pae Architecture: source Version: 5.4.13+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Description: acpi-modules-5.4.0-3-686-di - ACPI support modules (udeb) acpi-modules-5.4.0-3-686-pae-di - ACPI support modules (udeb) ata-modules-5.4.0-3-686-di - ATA disk modules (udeb) ata-modules-5.4.0-3-686-pae-di - ATA disk modules (udeb) btrfs-modules-5.4.0-3-686-di - BTRFS filesystem support (udeb) btrfs-modules-5.4.0-3-686-pae-di - BTRFS filesystem support (udeb) cdrom-core-modules-5.4.0-3-686-di - CDROM support (udeb) cdrom-core-modules-5.4.0-3-686-pae-di - CDROM support (udeb) compress-modules-5.4.0-3-686-di - lzo modules (udeb) compress-modules-5.4.0-3-686-pae-di - lzo modules (udeb) crc-modules-5.4.0-3-686-di - CRC modules (udeb) crc-modules-5.4.0-3-686-pae-di - CRC modules (udeb) crypto-dm-modules-5.4.0-3-686-di - devicemapper crypto module (udeb) crypto-dm-modules-5.4.0-3-686-pae-di - devicemapper crypto module (udeb) crypto-modules-5.4.0-3-686-di - crypto modules (udeb) crypto-modules-5.4.0-3-686-pae-di - crypto modules (udeb) efi-modules-5.4.0-3-686-di - EFI modules (udeb) efi-modules-5.4.0-3-686-pae-di - EFI modules (udeb) event-modules-5.4.0-3-686-di - Event support (udeb) event-modules-5.4.0-3-686-pae-di - Event support (udeb)
linux-signed-arm64_5.4.13+1_source.changes ACCEPTED into unstable, unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 19 Jan 2020 10:22:58 +0100
Source: linux-signed-arm64
Binary: kernel-image-5.4.0-3-arm64-di nic-modules-5.4.0-3-arm64-di
nic-wireless-modules-5.4.0-3-arm64-di nic-shared-modules-5.4.0-3-arm64-di
usb-serial-modules-5.4.0-3-arm64-di ppp-modules-5.4.0-3-arm64-di
cdrom-core-modules-5.4.0-3-arm64-di scsi-core-modules-5.4.0-3-arm64-di
scsi-modules-5.4.0-3-arm64-di scsi-nic-modules-5.4.0-3-arm64-di
loop-modules-5.4.0-3-arm64-di btrfs-modules-5.4.0-3-arm64-di
ext4-modules-5.4.0-3-arm64-di isofs-modules-5.4.0-3-arm64-di
jfs-modules-5.4.0-3-arm64-di xfs-modules-5.4.0-3-arm64-di
fat-modules-5.4.0-3-arm64-di md-modules-5.4.0-3-arm64-di
multipath-modules-5.4.0-3-arm64-di usb-modules-5.4.0-3-arm64-di
usb-storage-modules-5.4.0-3-arm64-di fb-modules-5.4.0-3-arm64-di
input-modules-5.4.0-3-arm64-di event-modules-5.4.0-3-arm64-di
nic-usb-modules-5.4.0-3-arm64-di sata-modules-5.4.0-3-arm64-di
i2c-modules-5.4.0-3-arm64-di crc-modules-5.4.0-3-arm64-di
crypto-modules-5.4.0-3-arm64-di crypto-dm-modules-5.4.0-3-arm64-di
efi-modules-5.4.0-3-arm64-di
ata-modules-5.4.0-3-arm64-di mmc-modules-5.4.0-3-arm64-di
nbd-modules-5.4.0-3-arm64-di squashfs-modules-5.4.0-3-arm64-di
uinput-modules-5.4.0-3-arm64-di compress-modules-5.4.0-3-arm64-di
leds-modules-5.4.0-3-arm64-di udf-modules-5.4.0-3-arm64-di
fuse-modules-5.4.0-3-arm64-di mtd-core-modules-5.4.0-3-arm64-di
linux-image-5.4.0-3-arm64 linux-image-arm64 linux-image-5.4.0-3-rt-arm64
linux-image-rt-arm64
Architecture: source
Version: 5.4.13+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Description:
ata-modules-5.4.0-3-arm64-di - ATA disk modules (udeb)
btrfs-modules-5.4.0-3-arm64-di - BTRFS filesystem support (udeb)
cdrom-core-modules-5.4.0-3-arm64-di - CDROM support (udeb)
compress-modules-5.4.0-3-arm64-di - lzo modules (udeb)
crc-modules-5.4.0-3-arm64-di - CRC modules (udeb)
crypto-dm-modules-5.4.0-3-arm64-di - devicemapper crypto module (udeb)
crypto-modules-5.4.0-3-arm64-di - crypto modules (udeb)
efi-modules-5.4.0-3-arm64-di - EFI modules (udeb)
event-modules-5.4.0-3-arm64-di - Event support (udeb)
ext4-modules-5.4.0-3-arm64-di - ext2/ext3/ext4 filesystem support (udeb)
fat-modules-5.4.0-3-arm64-di - FAT filesystem support (udeb)
fb-modules-5.4.0-3-arm64-di - Frame buffer support (udeb)
fuse-modules-5.4.0-3-arm64-di - FUSE modules (udeb)
i2c-modules-5.4.0-3-arm64-di - i2c support modules (udeb)
input-modules-5.4.0-3-arm64-di - Input devices support (udeb)
isofs-modules-5.4.0-3-arm64-di - ISOFS filesystem support (udeb)
jfs-modules-5.4.0-3-arm64-di - JFS filesystem support (udeb)
kernel-image-5.4.0-3-arm64-di - Linux kernel image and core modules for the
Debian installer (udeb)
leds-modules-5.4.0-3-arm64-di - LED modules (udeb)
linux-image-5.4.0-3-arm64 - ${unsigned:DescriptionShort} (signed)
linux-image-5.4.0-3-rt-arm64 - ${unsigned:DescriptionShort} (signed)
linux-image-arm64 - Linux for 64-bit ARMv8 machines (meta-package)
linux-image-rt-arm64 - Linux for 64-bit ARMv8 machines (meta-package)
loop-modules-5.4.0-3-arm64-di - Loopback filesystem support (udeb)
md-modules-5.4.0-3-arm64-di - RAID and LVM support (udeb)
mmc-modules-5.4.0-3-arm64-di - MMC/SD card modules (udeb)
mtd-core-modules-5.4.0-3-arm64-di - MTD core (udeb)
multipath-modules-5.4.0-3-arm64-di - Multipath support (udeb)
nbd-modules-5.4.0-3-arm64-di - Network Block Device modules (udeb)
nic-modules-5.4.0-3-arm64-di - NIC drivers (udeb)
nic-shared-modules-5.4.0-3-arm64-di - Shared NIC drivers (udeb)
nic-usb-modules-5.4.0-3-arm64-di - USB NIC drivers (udeb)
nic-wireless-modules-5.4.0-3-arm64-di - Wireless NIC drivers (udeb)
ppp-modules-5.4.0-3-arm64-di - PPP drivers (udeb)
sata-modules-5.4.0-3-arm64-di - SATA drivers (udeb)
scsi-core-modules-5.4.0-3-arm64-di - Core SCSI subsystem (udeb)
scsi-modules-5.4.0-3-arm64-di - SCSI drivers (udeb)
scsi-nic-modules-5.4.0-3-arm64-di - SCSI drivers for converged NICs (udeb)
squashfs-modules-5.4.0-3-arm64-di - squashfs modules (udeb)
udf-modules-5.4.0-3-arm64-di - UDF modules (udeb)
uinput-modules-5.4.0-3-arm64-di - uinput support (udeb)
usb-modules-5.4.0-3-arm64-di - USB support (udeb)
usb-serial-modules-5.4.0-3-arm64-di - USB serial drivers (udeb)
usb-storage-modules-5.4.0-3-arm64-di - USB storage support (udeb)
xfs-modules-5.4.0-3-arm64-di - XFS filesystem support (udeb)
Changes:
linux-signed-arm64 (5.4.13+1) unstable; urgency=medium
.
* Sign kernel from linux 5.4.13-1
.
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.9
- nvme_fc: add module to ops template to allow module references
- nvme-fc: fix double-free scenarios on hw queues
- drm/amdgpu: add check before enabling/disabling broadcast mode
- drm/amdgpu: add header line for power profile on Arcturus
- drm/amdgpu: add cache flush workaround to
linux-signed-i386_5.4.13+1_source.changes is NEW
Mapping sid to unstable. binary:linux-image-5.4.0-3-686 is NEW. binary:linux-image-5.4.0-3-686-pae is NEW. binary:linux-image-5.4.0-3-rt-686-pae is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of linux-signed-i386_5.4.13+1_source.changes
linux-signed-i386_5.4.13+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.4.13+1.dsc linux-signed-i386_5.4.13+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-arm64_5.4.13+1_source.changes is NEW
Mapping sid to unstable. binary:linux-image-5.4.0-3-arm64 is NEW. binary:linux-image-5.4.0-3-rt-arm64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
linux-signed-amd64_5.4.13+1_source.changes ACCEPTED into unstable, unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 19 Jan 2020 10:22:58 +0100
Source: linux-signed-amd64
Binary: kernel-image-5.4.0-3-amd64-di nic-modules-5.4.0-3-amd64-di
nic-wireless-modules-5.4.0-3-amd64-di nic-shared-modules-5.4.0-3-amd64-di
serial-modules-5.4.0-3-amd64-di usb-serial-modules-5.4.0-3-amd64-di
ppp-modules-5.4.0-3-amd64-di pata-modules-5.4.0-3-amd64-di
cdrom-core-modules-5.4.0-3-amd64-di firewire-core-modules-5.4.0-3-amd64-di
scsi-core-modules-5.4.0-3-amd64-di scsi-modules-5.4.0-3-amd64-di
scsi-nic-modules-5.4.0-3-amd64-di loop-modules-5.4.0-3-amd64-di
btrfs-modules-5.4.0-3-amd64-di ext4-modules-5.4.0-3-amd64-di
isofs-modules-5.4.0-3-amd64-di jfs-modules-5.4.0-3-amd64-di
xfs-modules-5.4.0-3-amd64-di fat-modules-5.4.0-3-amd64-di
md-modules-5.4.0-3-amd64-di multipath-modules-5.4.0-3-amd64-di
usb-modules-5.4.0-3-amd64-di usb-storage-modules-5.4.0-3-amd64-di
pcmcia-storage-modules-5.4.0-3-amd64-di fb-modules-5.4.0-3-amd64-di
input-modules-5.4.0-3-amd64-di event-modules-5.4.0-3-amd64-di
mouse-modules-5.4.0-3-amd64-di nic-pcmcia-modules-5.4.0-3-amd64-di
pcmcia-modules-5.4.0-3-amd64-di nic-usb-modules-5.4.0-3-amd64-di
sata-modules-5.4.0-3-amd64-di acpi-modules-5.4.0-3-amd64-di
i2c-modules-5.4.0-3-amd64-di crc-modules-5.4.0-3-amd64-di
crypto-modules-5.4.0-3-amd64-di crypto-dm-modules-5.4.0-3-amd64-di
efi-modules-5.4.0-3-amd64-di ata-modules-5.4.0-3-amd64-di
mmc-core-modules-5.4.0-3-amd64-di mmc-modules-5.4.0-3-amd64-di
nbd-modules-5.4.0-3-amd64-di squashfs-modules-5.4.0-3-amd64-di
speakup-modules-5.4.0-3-amd64-di uinput-modules-5.4.0-3-amd64-di
sound-modules-5.4.0-3-amd64-di compress-modules-5.4.0-3-amd64-di
udf-modules-5.4.0-3-amd64-di fuse-modules-5.4.0-3-amd64-di
mtd-core-modules-5.4.0-3-amd64-di rfkill-modules-5.4.0-3-amd64-di
linux-image-5.4.0-3-amd64 linux-image-amd64 linux-image-5.4.0-3-cloud-amd64
linux-image-cloud-amd64 linux-image-5.4.0-3-rt-amd64
linux-image-rt-amd64
Architecture: source
Version: 5.4.13+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Description:
acpi-modules-5.4.0-3-amd64-di - ACPI support modules (udeb)
ata-modules-5.4.0-3-amd64-di - ATA disk modules (udeb)
btrfs-modules-5.4.0-3-amd64-di - BTRFS filesystem support (udeb)
cdrom-core-modules-5.4.0-3-amd64-di - CDROM support (udeb)
compress-modules-5.4.0-3-amd64-di - lzo modules (udeb)
crc-modules-5.4.0-3-amd64-di - CRC modules (udeb)
crypto-dm-modules-5.4.0-3-amd64-di - devicemapper crypto module (udeb)
crypto-modules-5.4.0-3-amd64-di - crypto modules (udeb)
efi-modules-5.4.0-3-amd64-di - EFI modules (udeb)
event-modules-5.4.0-3-amd64-di - Event support (udeb)
ext4-modules-5.4.0-3-amd64-di - ext2/ext3/ext4 filesystem support (udeb)
fat-modules-5.4.0-3-amd64-di - FAT filesystem support (udeb)
fb-modules-5.4.0-3-amd64-di - Frame buffer support (udeb)
firewire-core-modules-5.4.0-3-amd64-di - Core FireWire drivers (udeb)
fuse-modules-5.4.0-3-amd64-di - FUSE modules (udeb)
i2c-modules-5.4.0-3-amd64-di - i2c support modules (udeb)
input-modules-5.4.0-3-amd64-di - Input devices support (udeb)
isofs-modules-5.4.0-3-amd64-di - ISOFS filesystem support (udeb)
jfs-modules-5.4.0-3-amd64-di - JFS filesystem support (udeb)
kernel-image-5.4.0-3-amd64-di - Linux kernel image and core modules for the
Debian installer (udeb)
linux-image-5.4.0-3-amd64 - ${unsigned:DescriptionShort} (signed)
linux-image-5.4.0-3-cloud-amd64 - ${unsigned:DescriptionShort} (signed)
linux-image-5.4.0-3-rt-amd64 - ${unsigned:DescriptionShort} (signed)
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-cloud-amd64 - Linux for x86-64 cloud (meta-package)
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package)
loop-modules-5.4.0-3-amd64-di - Loopback filesystem support (udeb)
md-modules-5.4.0-3-amd64-di - RAID and LVM support (udeb)
mmc-core-modules-5.4.0-3-amd64-di - MMC/SD/SDIO core modules (udeb)
mmc-modules-5.4.0-3-amd64-di - MMC/SD card modules (udeb)
mouse-modules-5.4.0-3-amd64-di - Mouse support (udeb)
mtd-core-modules-5.4.0-3-amd64-di - MTD core (udeb)
multipath-modules-5.4.0-3-amd64-di - Multipath support (udeb)
nbd-modules-5.4.0-3-amd64-di - Network Block Device modules (udeb)
nic-modules-5.4.0-3-amd64-di - NIC drivers (udeb)
nic-pcmcia-modules-5.4.0-3-amd64-di - Common PCMCIA NIC drivers (udeb)
nic-shared-modules-5.4.0-3-amd64-di - Shared NIC drivers (udeb)
nic-usb-modules-5.4.0-3-amd64-di - USB NIC drivers (udeb)
nic-wireless-modules-5.4.0-3-amd64-di - Wireless NIC drivers (udeb)
pata-modules-5.4.0-3-amd64-di - PATA drivers (udeb)
pcmcia-modules-5.4.0-3-amd64-di - Common PCMCIA drivers (udeb)
pcmcia-storage-modules-5.4.0-3-amd64-di - PCMCIA storage drivers (udeb)
ppp-modules-5.4.0-3-amd64-di - PPP drivers (udeb)
rfkill-modules-5.4.0-3-amd64-di - rfkill modules (udeb)
sata-modules-5.4.0-3-amd64-di - SATA drivers (udeb)
scsi-core-modules-5.4.0-3-amd64-di - Core SCSI
Processing of linux-signed-arm64_5.4.13+1_source.changes
linux-signed-arm64_5.4.13+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_5.4.13+1.dsc linux-signed-arm64_5.4.13+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-amd64_5.4.13+1_source.changes is NEW
Mapping sid to unstable. binary:linux-image-5.4.0-3-amd64 is NEW. binary:linux-image-5.4.0-3-cloud-amd64 is NEW. binary:linux-image-5.4.0-3-rt-amd64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of linux-signed-amd64_5.4.13+1_source.changes
linux-signed-amd64_5.4.13+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.4.13+1.dsc linux-signed-amd64_5.4.13+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled"
Hi Nicholas, all, Thank you very much for your answer and sorry for my delay... 6 janv. 2020 à 05:33 de nstee...@gmail.com: > While I'm very much a junior member of the team, I have noted similar > behaviour on a laptop as old as an X220 and wonder if it might be due to > Spectre mitigations. I have not noticed such log entries after > disabling hyperthreading. FYI, as someone who works with realtime audio > I've found that hyperthreading is detrimental to worst-case latency. > eg: after many hours trying to workaround troublesome unpredictable > latency spikes the solution to disable hyperthreading emerged as the > simplest solution. > I've just deactivated hyperthreading in my UEFI. Still the same warnings in journalctl :( At least, Internet resources indicate that's it's safer this way with HT deactivated (regarding MDS attacks) but I don't know (and really not anyone as it really depends on current CPU tasks) how my performances are impacted now... In your case, it seems to be a benefit but surely it's not always the case... Maybe I can just continue like this and restore HT if this is impossible to live with ;) >> >> > Have you > tried disabling CPU freq boost? When the ambient temperature is above > 27°C my X220 and X230 need to have boost disabled to avoid > overheating/throttling. > I've seen at least 2 ways to deactivate turbo boost: 1) echo "1" to /sys/devices/system/cpu/intel_pstate/no_turbo Visibly, as sysctl only works with /proc/sys (and not /sys), this needs to be set permanently via a systemd service. What do you think about this procedure: https://blog.christophersmart.com/2017/02/08/manage-intel-turbo-boost-with-systemd/? 2) modify MSR registers via wrmsr (https://askubuntu.com/a/619881). I don't know if there is persistance here... Do you use any of these? Something else? PS: My CPU is Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz. PPS: Even if it works, I don't know if I'm not gonna lose some more performances... Actually my main questions are: i) Are those temperature warnings legitimate? I mean maybe those warnings have been wrongly triggered because probes are not accurate? I'm not speaking about HW failure (my laptop is brand new) but maybe I just don't have the right driver somewhere... Indeed, it would be too bad to decrease all my performances with HT/turbo-boost disabled (security apart) whereas the journalctl warnings are wrong initially... ;) PS: I have installed intel-microcode 3.20191115.2~deb10u1. Still the same issues. I don't know if it's an issue but microcode module is blacklisted in /etc/modprobe.d/intel-microcode-blacklist.conf (it seems to be a precaution regarding unsafe updates). ii) Is it risky to do nothing about these temperature warnings? I have no idea what EC means (Embedded Controller?) but you said EC eventually shutdowns the laptop if need be. I presume it's not really beneficial from the user point of view as the current tasks will be shutdowned and some work/data might be lost during the process. Thanks again & Best regards :) l0f4r0
Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
On Fri, 12 Apr 2019 23:30:17 +0200 Frantisek Novak wrote: > as this does not have any direct impact on any other components I think it can be enabled independently. This is because the first write to the console bounds it to the FB and the output behavior works as usual. I just stumbled over this and became curious. Since i currently just directly boot the kernel via EFI stub i followed https://wiki.debian.org/BuildADebianKernelPackage and did give it a try. I was quite satisfied with the result. Are there any situations where this makes something worse? ( I see Ben tested this: https://salsa.debian.org/kernel-team/linux/commit/ b4995d6607608cd18181f47ee291a39868e678a7 ) Wolfgang
linux_5.4.13-1_source.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 19 Jan 2020 10:22:58 +0100 Source: linux Architecture: source Version: 5.4.13-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 948427 Changes: linux (5.4.13-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.9 - nvme_fc: add module to ops template to allow module references - nvme-fc: fix double-free scenarios on hw queues - drm/amdgpu: add check before enabling/disabling broadcast mode - drm/amdgpu: add header line for power profile on Arcturus - drm/amdgpu: add cache flush workaround to gfx8 emit_fence - nvme/pci: Fix write and poll queue types - nvme/pci: Fix read queue count - [armhf] iio: st_accel: Fix unused variable warning - PM / devfreq: Fix devfreq_notifier_call returning errno - PM / devfreq: Set scaling_max_freq to max on OPP notifier error - PM / devfreq: Don't fail devfreq_dev_release if not in list - afs: Fix afs_find_server lookups for ipv4 peers - afs: Fix SELinux setting security label on /afs - RDMA/cma: add missed unregister_pernet_subsys in init failure - rxe: correctly calculate iCRC for unaligned payloads - scsi: lpfc: Fix memory leak on lpfc_bsg_write_ebuf_set func - scsi: qla2xxx: Use explicit LOGO in target mode - scsi: qla2xxx: Drop superfluous INIT_WORK of del_work - scsi: qla2xxx: Don't call qlt_async_event twice - scsi: qla2xxx: Fix PLOGI payload and ELS IOCB dump length - scsi: qla2xxx: Configure local loop for N2N target - scsi: qla2xxx: Send Notify ACK after N2N PLOGI - scsi: qla2xxx: Don't defer relogin unconditonally - scsi: qla2xxx: Ignore PORT UPDATE after N2N PLOGI - scsi: iscsi: qla4xxx: fix double free in probe - scsi: libsas: stop discovering if oob mode is disconnected (CVE-2019-19965) - scsi: iscsi: Avoid potential deadlock in iscsi_if_rx func - [x86] staging/wlan-ng: add CRC32 dependency in Kconfig - drm/nouveau: Move the declaration of struct nouveau_conn_atom up a bit - drm/nouveau: Fix drm-core using atomic code-paths on pre-nv50 hardware - drm/nouveau/kms/nv50-: fix panel scaling - usb: gadget: fix wrong endpoint desc - net: make socket read/write_iter() honor IOCB_NOWAIT - afs: Fix mountpoint parsing - afs: Fix creation calls in the dynamic root to fail with EOPNOTSUPP - raid5: need to set STRIPE_HANDLE for batch head - md: raid1: check rdev before reference in raid1_sync_request func - [s390x] cpum_sf: Adjust sampling interval to avoid hitting sample limits - [s390x] cpum_sf: Avoid SBD overflow condition in irq handler - RDMA/counter: Prevent auto-binding a QP which are not tracked with res - IB/mlx4: Follow mirror sequence of device add during device removal - IB/mlx5: Fix steering rule of drop and count - xen-blkback: prevent premature module unload - xen/balloon: fix ballooned page accounting without hotplug enabled - PM / hibernate: memory_bm_find_bit(): Tighten node optimisation - ALSA: hda/realtek - Add Bass Speaker and fixed dac for bass speaker - ALSA: hda/realtek - Enable the bass speaker of ASUS UX431FLC - PCI: Add a helper to check Power Resource Requirements _PR3 existence - ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound to a driver - PCI: Fix missing inline for pci_pr3_present() - ALSA: hda - fixup for the bass speaker on Lenovo Carbon X1 7th gen - tcp: fix data-race in tcp_recvmsg() - shmem: pin the file in shmem_fault() if mmap_sem is dropped - taskstats: fix data-race - ALSA: hda - Downgrade error message for single-cmd fallback - netfilter: nft_tproxy: Fix port selector on Big Endian - block: add bio_truncate to fix guard_bio_eod - mm: drop mmap_sem before calling balance_dirty_pages() in write fault - ALSA: ice1724: Fix sleep-in-atomic in Infrasonic Quartet support code - ALSA: usb-audio: fix set_format altsetting sanity check - ALSA: usb-audio: set the interface format after resume on Dell WD19 - ALSA: hda - Apply sync-write workaround to old Intel platforms, too - ALSA: hda/realtek - Add headset Mic no shutup for ALC283 - [arm64,armhf] drm/sun4i: hdmi: Remove duplicate cleanup calls - [mips*] BPF: Disable MIPS32 eBPF JIT - [mips*] BPF: eBPF JIT: check for MIPS ISA compliance in Kconfig - [mips*] Avoid VDSO ABI breakage due to global register variable - media: pulse8-cec: fix lost cec_transmit_attempt_done() call - media: cec: CEC 2.0-only bcast messages were ignored - media: cec: avoid decrementing transmit_queue_sz if it is 0 - media: cec: check 'transmit_in_progress', not 'transmitting' - mm/memory_hotplug: shrink zones
Bug#948427: marked as done (modules.builtin.modinfo not included in signed image packages)
Your message dated Sun, 19 Jan 2020 12:00:11 +
with message-id
and subject line Bug#948427: fixed in linux 5.4.13-1
has caused the Debian Bug report #948427,
regarding modules.builtin.modinfo not included in signed image packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
948427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.2.6-1
Tags: patch
X-Debbugs-CC: Benjamin Poirier ,Michael Jeanson
As reported in originally https://bugs.debian.org/948257#88 with the
recent kmod update an issue with our signed packages was uncovered:
On Wed, Jan 08, 2020 at 01:45:21PM +0100, Salvatore Bonaccorso wrote:
> Hi Benjamin,
>
> On Wed, Jan 08, 2020 at 01:07:20PM +0100, Salvatore Bonaccorso wrote:
> > Hi Benjamin,
> >
> > On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
> > [...]
> > > Looks like the modules are built before lttng-sessiond is started:
> > > Setting up lttng-modules-dkms (2.11.0-2) ...
> > > Loading new lttng-modules-2.11.0 DKMS files...
> > > Building for 5.4.0-2-amd64
> > > Building initial module for 5.4.0-2-amd64
> > > Done.
> > >
> > > lttng-lib-ring-buffer.ko:
> > > Running module version sanity check.
> > >- Original module
> > > - No original module exists within this kernel
> > >- Installation
> > > - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
> > >
> > > [...]
> > >
> > > depmod...
> > >
> > > DKMS: install completed.
> > > Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> > > /etc/kernel/header_postinst.d/dkms:
> > > dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> > > Setting up sudo (1.8.29-1) ...
> > > Setting up babeltrace (1.5.7-2) ...
> > > Setting up liburcu6:amd64 (0.11.1-2) ...
> > > Setting up linux-headers-amd64 (5.4.8-1) ...
> > > Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> > > Setting up lttng-tools (2.11.0-3) ...
> > >
> > > Still, it doesn't work.
> > >
> > > > Simply restarting the sessiond should fix this.
> > >
> > > I tried restarting lttng-sessiond or rebooting the machine but it was no
> > > help, lttng-sessiond always reports:
> > > Error: Failed to load kmod library resources
> > > Warning: No kernel tracer available
> > >
> > > A quick look into the code shows that is:
> > > src/bin/lttng-sessiond/modprobe.c
> > > kmod_set_log_fn(*ctx, log_kmod, NULL);
> > > ret = kmod_load_resources(*ctx);
> > > if (ret < 0) {
> > > ERR("Failed to load kmod library resources");
> > > goto error;
> > > }
> > >
> > > I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> > > following:
> > > 8071 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-2-amd64/modules.dep.bin
> > > 8071 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-2-amd64/modules.alias.bin
> > > 8071 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> > > 8071 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
> > >
> > > On another machine which I haven't yet updated and where lttng still
> > > works, I see:
> > > 193519 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-1-amd64/modules.dep.bin
> > > 193519 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-1-amd64/modules.alias.bin
> > > 193519 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> > > 193519 lttng-sessiond 2 0
> > > /lib/modules/5.4.0-1-amd64/modules.builtin.bin
> > >
> > > Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> > > relevant but it's an empty file...
> > >
> > > After downgrading libkmod2 from
> > > Version: 26+20191223-1
> > > to
> > > Version: 26-3
> > > the issue with lttng is no longer apparent:
> > > root@vsid:/tmp# lttng list --kernel
> > > Kernel events:
> > > -
> > > asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type:
> > > tracepoint)
> > > asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type:
> > > tracepoint)
> > > asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type:
> > > tracepoint)
> > > [...]
> > >
> >
> > Should we track this in a separate bug from #948257?
>
> So here is what I think is part of what is going on (unless there is
> something broken in my analysis):
>
> Since 898490c010b5 ("moduleparam: Save information about built-in
> modules in separate file")[1] which is in 5.2-rc1, there is a new
>
Re: initramfs-tools_0.136_source.changes ACCEPTED into unstable
Debian FTP Masters writes: >* [835d584] mkinitramfs: Copy modules.builtin.bin into initramfs > (Closes: #948257) It's a bit depressing to see bugs hidden under the carpet instead of solved. But whatever. If you prefer adding a bug in mkinitramfs instead of fixing the problem, then I guess that's your decision. If anyone is interested in solving the kmod bug, then that is as simple as deleting a Debian patch, Which BTW seems to have been added in for the exact same reason: To hide another bug. Nice work Bjørn
linux_5.4.13-1_source.changes is NEW
binary:acpi-modules-5.4.0-3-686-di is NEW. binary:acpi-modules-5.4.0-3-686-pae-di is NEW. binary:acpi-modules-5.4.0-3-amd64-di is NEW. binary:affs-modules-5.4.0-3-4kc-malta-di is NEW. binary:affs-modules-5.4.0-3-5kc-malta-di is NEW. binary:affs-modules-5.4.0-3-loongson-3-di is NEW. binary:affs-modules-5.4.0-3-octeon-di is NEW. binary:ata-modules-5.4.0-3-4kc-malta-di is NEW. binary:ata-modules-5.4.0-3-5kc-malta-di is NEW. binary:ata-modules-5.4.0-3-686-di is NEW. binary:ata-modules-5.4.0-3-686-pae-di is NEW. binary:ata-modules-5.4.0-3-amd64-di is NEW. binary:ata-modules-5.4.0-3-arm64-di is NEW. binary:ata-modules-5.4.0-3-armmp-di is NEW. binary:ata-modules-5.4.0-3-loongson-3-di is NEW. binary:ata-modules-5.4.0-3-powerpc64le-di is NEW. binary:btrfs-modules-5.4.0-3-4kc-malta-di is NEW. binary:btrfs-modules-5.4.0-3-5kc-malta-di is NEW. binary:btrfs-modules-5.4.0-3-686-di is NEW. binary:btrfs-modules-5.4.0-3-686-pae-di is NEW. binary:btrfs-modules-5.4.0-3-amd64-di is NEW. binary:btrfs-modules-5.4.0-3-arm64-di is NEW. binary:btrfs-modules-5.4.0-3-armmp-di is NEW. binary:btrfs-modules-5.4.0-3-loongson-3-di is NEW. binary:btrfs-modules-5.4.0-3-marvell-di is NEW. binary:btrfs-modules-5.4.0-3-octeon-di is NEW. binary:btrfs-modules-5.4.0-3-powerpc64le-di is NEW. binary:btrfs-modules-5.4.0-3-s390x-di is NEW. binary:cdrom-core-modules-5.4.0-3-4kc-malta-di is NEW. binary:cdrom-core-modules-5.4.0-3-5kc-malta-di is NEW. binary:cdrom-core-modules-5.4.0-3-686-di is NEW. binary:cdrom-core-modules-5.4.0-3-686-pae-di is NEW. binary:cdrom-core-modules-5.4.0-3-amd64-di is NEW. binary:cdrom-core-modules-5.4.0-3-arm64-di is NEW. binary:cdrom-core-modules-5.4.0-3-armmp-di is NEW. binary:cdrom-core-modules-5.4.0-3-loongson-3-di is NEW. binary:cdrom-core-modules-5.4.0-3-marvell-di is NEW. binary:cdrom-core-modules-5.4.0-3-octeon-di is NEW. binary:cdrom-core-modules-5.4.0-3-powerpc64le-di is NEW. binary:cdrom-core-modules-5.4.0-3-s390x-di is NEW. binary:compress-modules-5.4.0-3-4kc-malta-di is NEW. binary:compress-modules-5.4.0-3-5kc-malta-di is NEW. binary:compress-modules-5.4.0-3-686-di is NEW. binary:compress-modules-5.4.0-3-686-pae-di is NEW. binary:compress-modules-5.4.0-3-amd64-di is NEW. binary:compress-modules-5.4.0-3-arm64-di is NEW. binary:compress-modules-5.4.0-3-armmp-di is NEW. binary:compress-modules-5.4.0-3-loongson-3-di is NEW. binary:compress-modules-5.4.0-3-marvell-di is NEW. binary:compress-modules-5.4.0-3-octeon-di is NEW. binary:compress-modules-5.4.0-3-powerpc64le-di is NEW. binary:compress-modules-5.4.0-3-s390x-di is NEW. binary:crc-modules-5.4.0-3-4kc-malta-di is NEW. binary:crc-modules-5.4.0-3-5kc-malta-di is NEW. binary:crc-modules-5.4.0-3-686-di is NEW. binary:crc-modules-5.4.0-3-686-pae-di is NEW. binary:crc-modules-5.4.0-3-amd64-di is NEW. binary:crc-modules-5.4.0-3-arm64-di is NEW. binary:crc-modules-5.4.0-3-armmp-di is NEW. binary:crc-modules-5.4.0-3-loongson-3-di is NEW. binary:crc-modules-5.4.0-3-marvell-di is NEW. binary:crc-modules-5.4.0-3-octeon-di is NEW. binary:crc-modules-5.4.0-3-powerpc64le-di is NEW. binary:crc-modules-5.4.0-3-s390x-di is NEW. binary:crypto-dm-modules-5.4.0-3-4kc-malta-di is NEW. binary:crypto-dm-modules-5.4.0-3-5kc-malta-di is NEW. binary:crypto-dm-modules-5.4.0-3-686-di is NEW. binary:crypto-dm-modules-5.4.0-3-686-pae-di is NEW. binary:crypto-dm-modules-5.4.0-3-amd64-di is NEW. binary:crypto-dm-modules-5.4.0-3-arm64-di is NEW. binary:crypto-dm-modules-5.4.0-3-armmp-di is NEW. binary:crypto-dm-modules-5.4.0-3-loongson-3-di is NEW. binary:crypto-dm-modules-5.4.0-3-marvell-di is NEW. binary:crypto-dm-modules-5.4.0-3-octeon-di is NEW. binary:crypto-dm-modules-5.4.0-3-powerpc64le-di is NEW. binary:crypto-dm-modules-5.4.0-3-s390x-di is NEW. binary:crypto-modules-5.4.0-3-4kc-malta-di is NEW. binary:crypto-modules-5.4.0-3-5kc-malta-di is NEW. binary:crypto-modules-5.4.0-3-686-di is NEW. binary:crypto-modules-5.4.0-3-686-pae-di is NEW. binary:crypto-modules-5.4.0-3-amd64-di is NEW. binary:crypto-modules-5.4.0-3-arm64-di is NEW. binary:crypto-modules-5.4.0-3-armmp-di is NEW. binary:crypto-modules-5.4.0-3-loongson-3-di is NEW. binary:crypto-modules-5.4.0-3-marvell-di is NEW. binary:crypto-modules-5.4.0-3-octeon-di is NEW. binary:crypto-modules-5.4.0-3-powerpc64le-di is NEW. binary:crypto-modules-5.4.0-3-s390x-di is NEW. binary:dasd-extra-modules-5.4.0-3-s390x-di is NEW. binary:dasd-modules-5.4.0-3-s390x-di is NEW. binary:efi-modules-5.4.0-3-686-di is NEW. binary:efi-modules-5.4.0-3-686-pae-di is NEW. binary:efi-modules-5.4.0-3-amd64-di is NEW. binary:efi-modules-5.4.0-3-arm64-di is NEW. binary:efi-modules-5.4.0-3-armmp-di is NEW. binary:event-modules-5.4.0-3-4kc-malta-di is NEW. binary:event-modules-5.4.0-3-5kc-malta-di is NEW. binary:event-modules-5.4.0-3-686-di is NEW. binary:event-modules-5.4.0-3-686-pae-di is NEW. binary:event-modules-5.4.0-3-amd64-di is NEW. binary:event-modules-5.4.0-3-arm64-di is NEW. binary:event-modules-5.4.0-3-armmp-di is NEW.
Processing of linux_5.4.13-1_source.changes
linux_5.4.13-1_source.changes uploaded successfully to localhost along with the files: linux_5.4.13-1.dsc linux_5.4.13.orig.tar.xz linux_5.4.13-1.debian.tar.xz linux_5.4.13-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
