Processed: Bookworm too
Processing commands for cont...@bugs.debian.org: > found 1067006 1:2.6.2-4 Bug #1067006 [nfs-common] rpc-statd.service: State 'stop-sigterm' timed out. Killing. Marked as found in versions nfs-utils/1:2.6.2-4. > End of message, stopping processing here. Please contact me if you need assistance. -- 1067006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: argon2 tool doesn't properly link against pthread
Processing control commands: > reassign -1 initramfs-tools Bug #1069912 [argon2] argon2: argon2 tool doesn't properly link against pthread Bug reassigned from package 'argon2' to 'initramfs-tools'. No longer marked as found in versions argon2/0~20190702+dfsg-4. Ignoring request to alter fixed versions of bug #1069912 to the same values previously set > severity -1 important Bug #1069912 [initramfs-tools] argon2: argon2 tool doesn't properly link against pthread Severity set to 'important' from 'wishlist' > retitle -1 copy_exec doesn't detect libgcc dependency anymore when pthread is > used Bug #1069912 [initramfs-tools] argon2: argon2 tool doesn't properly link against pthread Changed Bug title to 'copy_exec doesn't detect libgcc dependency anymore when pthread is used' from 'argon2: argon2 tool doesn't properly link against pthread'. -- 1069912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069870: linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware
Processing control commands: > reassign -1 src:firmware-nonfree 20230625-2 Bug #1069870 [src:linux] linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware Bug reassigned from package 'src:linux' to 'src:firmware-nonfree'. No longer marked as found in versions linux/6.7.7-1. Ignoring request to alter fixed versions of bug #1069870 to the same values previously set Bug #1069870 [src:firmware-nonfree] linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware Marked as found in versions firmware-nonfree/20230625-2. -- 1069870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1069870 to linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware
Processing commands for cont...@bugs.debian.org: > retitle 1069870 linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware Bug #1069870 [src:linux] linux-image-6.7.7-686-pae: please enable i915 mtl_* modules Changed Bug title to 'linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware' from 'linux-image-6.7.7-686-pae: please enable i915 mtl_* modules'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: FTBFS on mips64el in lsfd/mkfds-multiplexing-pselect6 test et al
Processing control commands: > forwarded -1 https://github.com/util-linux/util-linux/issues/2867 > https://lore.kernel.org/all/20240328-mips_save_syscall-v1-1-9e1d62d69...@flygoat.com/ Bug #1068365 [src:linux] util-linux: FTBFS on mips64el in lsfd/mkfds-multiplexing-pselect6 test et al Changed Bug forwarded-to-address to 'https://github.com/util-linux/util-linux/issues/2867 https://lore.kernel.org/all/20240328-mips_save_syscall-v1-1-9e1d62d69...@flygoat.com/' from 'https://github.com/util-linux/util-linux/issues/2867'. -- 1068365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1068365 to src:linux, affects 1068365
Processing commands for cont...@bugs.debian.org: > reassign 1068365 src:linux Bug #1068365 [src:util-linux] util-linux: FTBFS on mips64el in lsfd/mkfds-multiplexing-pselect6 test et al Bug reassigned from package 'src:util-linux' to 'src:linux'. No longer marked as found in versions util-linux/2.40-1. Ignoring request to alter fixed versions of bug #1068365 to the same values previously set > affects 1068365 src:util-linux Bug #1068365 [src:linux] util-linux: FTBFS on mips64el in lsfd/mkfds-multiplexing-pselect6 test et al Added indication that 1068365 affects src:util-linux > thanks Stopping processing here. Please contact me if you need assistance. -- 1068365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)
Processing control commands: > tags -1 unreproducible - fixed-upstream Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110) Added tag(s) unreproducible. Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110) Removed tag(s) fixed-upstream. > close -1 Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110) Marked Bug as done -- 1023192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:linux
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:linux > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1023192 (http://bugs.debian.org/1023192) > # Bug title: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: > Reading Intel version command failed (-110) > # * http://bugzilla.kernel.org/show_bug.cgi?id=215167 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> OBSOLETE > # * closed upstream > tags 1023192 + fixed-upstream Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110) Added tag(s) fixed-upstream. > usertags 1023192 - status-NEW Usertags were: status-NEW. There are now no usertags set. > usertags 1023192 + status-RESOLVED resolution-OBSOLETE There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. > # remote status report for #1058890 (http://bugs.debian.org/1058890) > # Bug title: linux-image-6.1.0-16-amd64 breaks suspend > # * http://bugzilla.kernel.org/show_bug.cgi?id=218538 > # * remote status changed: (?) -> NEW > usertags 1058890 + status-NEW There were no usertags set. Usertags are now: status-NEW. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023192 1058890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059525: marked as done (linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD)
Your message dated Thu, 25 Apr 2024 08:48:22 +0200 with message-id and subject line Re: Bug#1059525: linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD has caused the Debian Bug report #1059525, regarding linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD 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.) -- 1059525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.67-1 Severity: serious X-Debbugs-Cc: yelcnce01w76dbotr...@gmail.com Dear Maintainer, * What led up to the situation? I started Debian 12 on an Intel NUC with Crucial P5 Plus NVME and noticed that Secure Boot is not active, only if an NVME is installed. When the NVME is fitted, the Debian Live Stick also changes the secure boot state to disabled. This does not happen with Debian if the NVME is removed and only one HDD is used. In Bios Secure Boot is enabled. With NVME and active Secure Boot, Kernel starts properly dmesg | grep -i secure [0.00] secureboot: Secure boot disabled [1.294078] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [1.294088] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f' mokutil --sb-state This system doesn't support Secure Boot With NVME and active Secure Boot and Mainboard Lockdown-Pins dmesg | grep -i secure [0.00] Kernel is locked down from EFI Secure Boot; see man kernel_lockdown.7 [0.00] secureboot: Secure boot enabled [1.287502] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [1.287513] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f' [1.295587] integrity: Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' mokutil --sb-state SecureBoot enabled * What exactly did you do (or not do) that was effective (or ineffective)? The behavior changes when I set the lockdown-pins on the mainboard from the Intel NUC. Then Secure Boot is activ with these NVME. * What was the outcome of this action? * What outcome did you expect instead? Secure Boot should always be active and if not, Debian should not start. -- Package-specific info: ** Version: Linux version 6.1.0-16-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-16-amd64 root=/dev/mapper/lvgdeb-debix ro rootflags=subvol=@rootfs quiet ** Not tainted ** Kernel log: [ 13.280197] BTRFS info: devid 1 device path /dev/mapper/lvgdeb-debix changed to /dev/dm-1 scanned by (udev-worker) (590) [ 13.280714] BTRFS info: devid 1 device path /dev/dm-1 changed to /dev/mapper/lvgdeb-debix scanned by (udev-worker) (590) [ 13.298823] intel_pmc_core INT33A1:00: initialized [ 13.317186] resource sanity check: requesting [mem 0xfedc-0xfedc], which spans more than pnp 00:03 [mem 0xfedc-0xfedc7fff] [ 13.317191] caller igen6_probe+0x199/0x7d0 [igen6_edac] mapping multiple BARs [ 13.321118] EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV :00:00.0 (INTERRUPT) [ 13.321700] Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found [ 13.321729] Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at index 1 [ 13.324335] EDAC MC1: Giving out device to module igen6_edac controller Intel_client_SoC MC#1: DEV :00:00.0 (INTERRUPT) [ 13.324397] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR [ 13.324399] EDAC igen6 MC1: ADDR 0x7fffe0 [ 13.324400] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR [ 13.324401] EDAC igen6 MC0: ADDR 0x7fffe0 [ 13.325163] EDAC igen6: v2.5.1 [ 13.389497] ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only [ 13.412053] mei_me :00:16.0: enabling device ( -> 0002) [ 13.422361] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 13.422472] cfg80211: Loaded X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf' [ 13.422560] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b
Bug#1067054: marked as done (Debian 12 - Copy files on USB 3)
Your message dated Thu, 25 Apr 2024 08:49:18 +0200 with message-id and subject line Re: Bug#1067054: Debian 12 - Copy files on USB 3 has caused the Debian Bug report #1067054, regarding Debian 12 - Copy files on USB 3 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.) -- 1067054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel Version: 6.1.76-1 (2024-02-01) Severity: critical Bug Description: Good morning, I noticed a problem with Debian 12 and USB 3. When I copy a large volume of data +/- 150 Gb onto a 2.5 inch SSD integrated into an external enclosure (Satechi) which has a USB 3 type C socket and this enclosure is plugged into a USB 3 A socket on my PC, the copy cuts out after a while (+/- 20%), there is a crash. If I use a USB 3 C socket on my PC it seems to make the problem worse. Same thing if I restore a 250 GB disk image, it also crashes. If I do the same restoration job but on a 2 A USB socket, everything works perfectly, except that it takes a lot of time... If I use an M.2 2280 drive also integrated into an external enclosure with a USB 3 type C socket, everything works fine. If I use an SD card connected to an SD card reader connected via USB 3 to my machine it also works perfectly. Debian and its kernel do not seem to appreciate 2.5 inch SSDs integrated into external enclosures with a USB 3 type C socket... Please try to fix this... Best regards.--- End Message --- --- Begin Message --- On Wed, Apr 17, 2024 at 01:27:13AM +0200, pham...@bluewin.ch wrote: > It is stable when you initialize the disk in MBR/MS-DOS format, but only with > a USB A to USB C cable, if you use a USB c to USB-C cable the problems > persist. Hardware problem, nothing Debian can do about.--- End Message ---
Bug#1069735: marked as done (general: atlantic driver doesn't work on thinkpad)
Your message dated Thu, 25 Apr 2024 08:44:26 +0200 with message-id and subject line Re: Bug#1069735: general: atlantic driver doesn't work on thinkpad has caused the Debian Bug report #1069735, regarding general: atlantic driver doesn't work on thinkpad 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.) -- 1069735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Dear Maintainer, I have a problem with atlantic driver on debian testing kernel 6.6.15. When I plug my device (Sonnet tech 10G adapter thunderbolt 3), the device will not appear in lspci but it detect from dmesg command. On an ubuntu, the device works. This is traces : ``` root@Elliot:~# lspci -tv -[:00]-+-00.0 Intel Corporation Coffee Lake HOST and DRAM Controller +-02.0 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] +-04.0 Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem +-08.0 Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model +-12.0 Intel Corporation Cannon Point-LP Thermal Controller +-14.0 Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller +-14.2 Intel Corporation Cannon Point-LP Shared SRAM +-14.3 Intel Corporation Cannon Point-LP CNVi [Wireless-AC] +-15.0 Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 +-16.0 Intel Corporation Cannon Point-LP MEI Controller #1 +-1c.0-[01]00.0 Genesys Logic, Inc GL9750 SD Host Controller +-1c.4-[02-3a]00.0-[03-3a]--+-00.0-[04]00.0 Intel Corporation JHL6240 Thunderbolt 3 NHI (Low Power) [Alpine Ridge LP 2016] | +-01.0-[05-39]-- | \-02.0-[3a]00.0 Intel Corporation JHL6240 Thunderbolt 3 USB 3.1 Controller (Low Power) [Alpine Ridge LP 2016] +-1d.0-[3c]-- +-1d.4-[3d]00.0 Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) +-1f.0 Intel Corporation Cannon Point-LP LPC Controller +-1f.3 Intel Corporation Cannon Point-LP High Definition Audio Controller +-1f.4 Intel Corporation Cannon Point-LP SMBus Controller +-1f.5 Intel Corporation Cannon Point-LP SPI Controller \-1f.6 Intel Corporation Ethernet Connection (6) I219-V root@Elliot:~# modinfo atlantic filename: /lib/modules/6.6.15-amd64/kernel/drivers/net/ethernet/aquantia/atlantic/atlantic.ko.xz description:Marvell (Aquantia) Corporation(R) Network Driver author: Marvell license:GPL v2 alias: pci:v1D6Ad11C0sv*sd*bc*sc*i* alias: pci:v1D6Ad34C0sv*sd*bc*sc*i* alias: pci:v1D6Ad12C0sv*sd*bc*sc*i* alias: pci:v1D6Ad14C0sv*sd*bc*sc*i* alias: pci:v1D6Ad04C0sv*sd*bc*sc*i* alias: pci:v1D6Ad93C0sv*sd*bc*sc*i* alias: pci:v1D6Ad94C0sv*sd*bc*sc*i* alias: pci:v1D6Ad00C0sv*sd*bc*sc*i* alias: pci:v1D6Ad92B1sv*sd*bc*sc*i* alias: pci:v1D6Ad91B1sv*sd*bc*sc*i* alias: pci:v1D6Ad89B1sv*sd*bc*sc*i* alias: pci:v1D6Ad88B1sv*sd*bc*sc*i* alias: pci:v1D6Ad87B1sv*sd*bc*sc*i* alias: pci:v1D6Ad80B1sv*sd*bc*sc*i* alias: pci:v1D6Ad12B1sv*sd*bc*sc*i* alias: pci:v1D6Ad11B1sv*sd*bc*sc*i* alias: pci:v1D6Ad09B1sv*sd*bc*sc*i* alias: pci:v1D6Ad08B1sv*sd*bc*sc*i* alias: pci:v1D6Ad07B1sv*sd*bc*sc*i* alias: pci:v1D6Ad00B1sv*sd*bc*sc*i* alias: pci:v1D6AdD109sv*sd*bc*sc*i* alias: pci:v1D6AdD108sv*sd*bc*sc*i* alias: pci:v1D6AdD107sv*sd*bc*sc*i* alias: pci:v1D6AdD100sv*sd*bc*sc*i* alias: pci:v1D6Ad0001sv*sd*bc*sc*i* depends:macsec retpoline: Y intree: Y name: atlantic vermagic: 6.6.15-amd64 SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:21:EC:AB:7F:99:B0:2B:29:F0:14:9D:30:26:B6:2F:1B:F0:91:ED:13 sig_hashalgo: sha256 signature: 30:65:02:31:00:C5:7E:D8:EA:3A:0A:D9:65:E4:44:64:B7:AD:C6:58: 83:27:E6:87:BE:DB:4C:F8:17:68:D1:CE:CA:49:45:27:17:20:9A:67
Processed: reassign 1069777 to cryptsetup-initramfs
Processing commands for cont...@bugs.debian.org: > # Guessing that crypttab support is provided by cryptsetup-initramfs > # instead of initramfs-tools itself. > reassign 1069777 cryptsetup-initramfs Bug #1069777 [initramfs-tools] initramfs-tools: Bug/feature request: better handling of /etc/crypttab not ending in new line character Bug reassigned from package 'initramfs-tools' to 'cryptsetup-initramfs'. No longer marked as found in versions initramfs-tools/0.142. Ignoring request to alter fixed versions of bug #1069777 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1069735 src:linux 6.6.15-2 Bug #1069735 [linux-image-6.6.15-amd64] general: atlantic driver doesn't work on thinkpad Bug reassigned from package 'linux-image-6.6.15-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1069735 to the same values previously set Ignoring request to alter fixed versions of bug #1069735 to the same values previously set Bug #1069735 [src:linux] general: atlantic driver doesn't work on thinkpad Marked as found in versions linux/6.6.15-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1069735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassigning bugreport to kernel
Processing commands for cont...@bugs.debian.org: > reassign 1069735 linux-image-6.6.15-amd64 Bug #1069735 [general] general: atlantic driver doesn't work on thinkpad Bug reassigned from package 'general' to 'linux-image-6.6.15-amd64'. Ignoring request to alter found versions of bug #1069735 to the same values previously set Ignoring request to alter fixed versions of bug #1069735 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068189: marked as done (debhelper: --link-doc checking for known packages makes linux-signed build FTBFS)
Your message dated Wed, 24 Apr 2024 11:00:10 +
with message-id
and subject line Bug#1068189: fixed in linux 6.7.12-1
has caused the Debian Bug report #1068189,
regarding debhelper: --link-doc checking for known packages makes linux-signed
build FTBFS
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.)
--
1068189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debhelper
Version: 13.15
Severity: serious
Tags: ftbfs
Justification: Regression for other package builds, FTBFS
X-Debbugs-Cc: car...@debian.org,debian-kernel@lists.debian.org
Control: affects -1 + src:linux,src:linux-signed-amd64,src:linux-signed-arm64
Hi Niels,
Not fully investigated, but starting to fill a bugreport. I noticed
that the src:linux pipeline on salsa started to fail for the
jobs in th build-signed stage (in the build-signed job).
https://salsa.debian.org/carnil/linux/-/jobs/5527774
(and for saving the output):
dh_installdocs --link-doc=linux-headers-6.7+unreleased-cloud-amd64
dh_installdocs: error: Requested unknown package
linux-headers-6.7+unreleased-cloud-amd64 via --link-doc, expected one of:
linux-image-6.7+unreleased-amd64 linux-image-amd64 linux-headers-amd64
linux-image-6.7+unreleased-cloud-amd64 linux-image-cloud-amd64
linux-headers-cloud-amd64 linux-image-6.7+unreleased-rt-amd64
linux-image-rt-amd64 linux-headers-rt-amd64
make[2]: *** [debian/rules.real:81: binary_meta] Error 25
make[1]: *** [debian/rules.gen:21: binary-arch_amd64_none_cloud-amd64_meta]
Error 2
make: *** [debian/rules:19: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
(attached as well the raw log)
I'm not 100% sure yet, this might be a problem in our packaging in
which case we can re-eassign. But it only got triggered with the
change recently in debhelper:
https://salsa.debian.org/debian/debhelper/-/commit/dec5cfad00e2abd9ee3594f90c93f3fa42bb73ff
Regards,
Salvatore
5527774.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.7.12-1
Done: Salvatore Bonaccorso
We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso (supplier of updated linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Apr 2024 09:42:56 +0200
Source: linux
Architecture: source
Version: 6.7.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 1068189
Changes:
linux (6.7.12-1) unstable; urgency=medium
.
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.10
- [arm64] dmaengine: fsl-edma: utilize common dt-binding header file
- [arm64] dmaengine: fsl-edma: correct max_segment_size setting
- xfrm: Clear low order bits of ->flowi4_tos in decode_session4().
- xfrm: Pass UDP encapsulation in TX packet offload
- net: lan78xx: fix runtime PM count underflow on link stop
- ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
- i40e: disable NAPI right after disabling irqs when handling xsk_pool
- ice: reorder disabling IRQ and NAPI in ice_qp_dis
- ice: replace ice_vf_recreate_vsi() with ice_vf_reconfig_vsi()
- ice: reconfig host after changing MSI-X on VF
- Revert "net/mlx5: Block entering switchdev mode with ns inconsistency"
- Revert "net/mlx5e: Check the number of elements before walk TC
rhashtable"
- net/mlx5: E-switch, Change flow rule destination checking
- net/mlx5: Fix fw reporter diagnose output
- net/mlx5: Check capability for fw_reset
- net/mlx5e: Change the warning when ignore_flow_level is not supported
- net/mlx5e: Fix MACsec state loss upon state update in offload path
- net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission
tracking
occurs after populating the metadata_map
Processed: reassign 1069747 to src:linux, closing 1069747
Processing commands for cont...@bugs.debian.org: > reassign 1069747 src:linux Bug #1069747 [linux-image-6.6.13+bpo-amd64] ext4 data loss issue in backport kernels still unfixed? Bug reassigned from package 'linux-image-6.6.13+bpo-amd64' to 'src:linux'. No longer marked as found in versions 6.6.13. Ignoring request to alter fixed versions of bug #1069747 to the same values previously set > close 1069747 Bug #1069747 [src:linux] ext4 data loss issue in backport kernels still unfixed? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1069747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20
Processing control commands: > reassign -1 src:linux Bug #1069642 [linux-image-6.1.0-20-amd64] linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20 Bug reassigned from package 'linux-image-6.1.0-20-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1069642 to the same values previously set Ignoring request to alter fixed versions of bug #1069642 to the same values previously set > severity -1 normal Bug #1069642 [src:linux] linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20 Severity set to 'normal' from 'grave' > tags -1 moreinfo Bug #1069642 [src:linux] linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20 Added tag(s) moreinfo. -- 1069642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2
Processing control commands: > tag -1 -moreinfo +upstream Bug #1069301 [src:linux] linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2 Removed tag(s) moreinfo. Bug #1069301 [src:linux] linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2 Added tag(s) upstream. > forwarded -1 > https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/ Bug #1069301 [src:linux] linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2 Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/'. -- 1069301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen
Processing commands for cont...@bugs.debian.org:
> reopen 1067006
Bug #1067006 {Done: Salvatore Bonaccorso } [nfs-common]
rpc-statd.service: State 'stop-sigterm' timed out. Killing.
Bug reopened
Ignoring request to alter fixed versions of bug #1067006 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1067006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1069598 to src:linux, forcibly merging 1069605 1069598
Processing commands for cont...@bugs.debian.org: > reassign 1069598 src:linux Bug #1069598 [cifs-utils] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Bug reassigned from package 'cifs-utils' to 'src:linux'. No longer marked as found in versions cifs-utils/2:7.0-2. Ignoring request to alter fixed versions of bug #1069598 to the same values previously set > forcemerge 1069605 1069598 Bug #1069605 [src:linux] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Bug #1069598 [src:linux] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Marked as found in versions linux/6.1.85-1. Merged 1069598 1069605 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069598 1069605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1069605 to src:linux, found 1069605 in linux/6.1.85-1, notfound 1069605 in linux/6.1.76-1
Processing commands for cont...@bugs.debian.org: > # seems to be a kernel regression > reassign 1069605 src:linux Bug #1069605 [cifs-utils] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Bug reassigned from package 'cifs-utils' to 'src:linux'. No longer marked as found in versions cifs-utils/2:7.0-2. Ignoring request to alter fixed versions of bug #1069605 to the same values previously set > found 1069605 linux/6.1.85-1 Bug #1069605 [src:linux] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Marked as found in versions linux/6.1.85-1. > notfound 1069605 linux/6.1.76-1 Bug #1069605 [src:linux] cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing Ignoring request to alter found versions of bug #1069605 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069244: marked as done (nfs: Have not changed nfs version, but reboot of server says nfs versions do not match)
Your message dated Sat, 20 Apr 2024 11:33:33 +0200 with message-id and subject line Re: Bug#1069244: Fixed - but still an open comment has caused the Debian Bug report #1069244, regarding nfs: Have not changed nfs version, but reboot of server says nfs versions do not match 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.) -- 1069244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: klibc-utils Version: 2.0.6-1+deb10u1 Severity: critical File: nfs Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Distributor ID: Bunsenlabs Description:BunsenLabs GNU/Linux 10.5 (Lithium) Release:10.5 Codename: buster Architecture: x86_64 Kernel: Linux 5.10.0-0.deb10.16-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages klibc-utils depends on: ii libklibc 2.0.6-1+deb10u1 klibc-utils recommends no packages. klibc-utils suggests no packages. -- no debconf information First some background: I am an experienced software engineer who spend many years in the software industry, mostly as a software develeper in the Integrated Circuit Compter-Aided Design industry. I say this to let you know I have a very good background in software. Second, I filed this as a klibc-utils bug. This is bogus! When entering the report, I did not see and way to report the problem as an NFS problem. I may have missed that during the report process. My apologies if I did miss it. I repeat, this is an NFS problem. The problem I have run into is that when installing a new instance of the Bunsenlabs Lithium release I have frequently run into the message: mount.nfs: requested NFS version or transport protocol is not supported This error comes up despite the fact that I am running the same default version of nfs on both the client and on the server. In the past, I have been able to resolve the issue by restarting the nfs server on the LAN server. This does not work now. So far I have spent roughly 10 hours trying to get my internal network up and running, and I expect to spend a good part of today getting my network backup. FYI, I have internet service on each of my computers, but internally I cannot mount server file systems on my clients. However, even when this fixes the problem, the error message is still a bug! Why do I say this? This is true, because in recent years, I have been using NFS, version 3, and nothing else. The error message itself is wrong. If nothing else, the software can be improved by reporting which version of nfs is found on the server and which version is found on the client. My expectation is that the error detecting message will then reveal that the versions are NOT incompatible. So please, provide the additional information. I will then consider this problem fixed. My expectation is that you will then receive reports from myself and others that we are receiving the message despite the fact that the nfs versions are identical. I would not be surprised if the error a result of fact that the client and server have different versions of one or more library files. This is only speculation. My email was given as jjanderson52...@gmail.com. This is a valid email address. Just to let you know I do not look at it everyday, but I will try to check regularly so that I can provide additional information if you may need it. Whoever receives this message, I would appreciate that you acknowledge that you are looking into the problem. Thank you for taking the time! Regards, Jim Anderson --- End Message --- --- Begin Message --- On Thu, Apr 18, 2024 at 02:23:06PM -0400, Jim Anderson wrote: > > Thankfully, I reinstalled the Boron release on my LAN server and was able to > get the nfs server running properly. I have worked around the flaw in the > system. As indicated by Thorsten, you are reporting this in a bug tracker of the wrong distribution. Also, you are reporting this in the bug tracker of the wrong package. > My though rema
Processed: Re: Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2
Processing control commands: > tags -1 + moreinfo Bug #1069301 [src:linux] linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2 Added tag(s) moreinfo. -- 1069301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069244: nfs: Have not changed nfs version, but reboot of server says nfs versions do not match
Processing commands for cont...@bugs.debian.org: > severity 1069244 important Bug #1069244 [klibc-utils] nfs: Have not changed nfs version, but reboot of server says nfs versions do not match Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1069244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1069092 is forwarded to https://lore.kernel.org/linux-cifs/zibcsoc0yf_i8...@eldamar.lan/ ...
Processing commands for cont...@bugs.debian.org: > forwarded 1069092 > https://lore.kernel.org/linux-cifs/zibcsoc0yf_i8...@eldamar.lan/ Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-cifs/zibcsoc0yf_i8...@eldamar.lan/'. Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-cifs/zibcsoc0yf_i8...@eldamar.lan/'. > tags 1069092 - moreinfo Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Removed tag(s) moreinfo. Removed tag(s) moreinfo. > tags 1069092 + upstream Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Added tag(s) upstream. Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1069102 in 6.1.82-1
Processing commands for cont...@bugs.debian.org: > found 1069102 6.1.82-1 Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Marked as found in versions linux/6.1.82-1. Marked as found in versions linux/6.1.82-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Re: Bug#1069077: es8316 driver causes kernel oops / panic on rockpro64
Processing control commands: > found -1 6.6.15-2 Bug #1069077 [src:linux] es8316 driver causes kernel oops / panic on rockpro64 Marked as found in versions linux/6.6.15-2. -- 1069077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069082: linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0
Processing control commands: > forwarded -1 > https://lore.kernel.org/regressions/zh7flxvnddfat...@eldamar.lan/T/#u Bug #1069082 [src:linux] linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0 Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/zh7flxvnddfat...@eldamar.lan/T/#u'. -- 1069082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1069082, tagging 1069082
Processing commands for cont...@bugs.debian.org: > tags 1069082 - moreinfo Bug #1069082 [src:linux] linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0 Removed tag(s) moreinfo. > tags 1069082 + upstream Bug #1069082 [src:linux] linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1069131 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1069131 src:linux Bug #1069131 [linux-image-6.1.0-20-amd64] e1000e driver Network Card Detected Hardware Unit Hang Bug reassigned from package 'linux-image-6.1.0-20-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1069131 to the same values previously set Ignoring request to alter fixed versions of bug #1069131 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069102: linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares
Processing control commands: > tags -1 + moreinfo Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Ignoring request to alter tags of bug #1069102 to the same tags previously set Ignoring request to alter tags of bug #1069092 to the same tags previously set -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069102: linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares
Processing control commands: > tags -1 + moreinfo Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Ignoring request to alter tags of bug #1069092 to the same tags previously set Ignoring request to alter tags of bug #1069102 to the same tags previously set -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069102: linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares
Processing control commands: > tags -1 + moreinfo Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Added tag(s) moreinfo. Added tag(s) moreinfo. -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069082: linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0
Processing control commands: > tags -1 + moreinfo Bug #1069082 [src:linux] linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0 Added tag(s) moreinfo. -- 1069082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1069092 1069102
Processing commands for cont...@bugs.debian.org: > forcemerge 1069092 1069102 Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Bug #1069102 [src:linux] linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares Severity set to 'normal' from 'important' Merged 1069092 1069102 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 1069102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1069092 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1069092 src:linux 6.1.85-1 Bug #1069092 [linux-image-amd64] Kernel 6.1.85-1 breaking CIFS mounts? Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.1.85+1. Ignoring request to alter fixed versions of bug #1069092 to the same values previously set Bug #1069092 [src:linux] Kernel 6.1.85-1 breaking CIFS mounts? Marked as found in versions linux/6.1.85-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > submitter 1069077 ! Bug #1069077 [src:linux] es8316 driver causes kernel oops / panic on rockpro64 Changed Bug submitter to 'Forest ' from 'Forest '. > thanks. Stopping processing here. Please contact me if you need assistance. -- 1069077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069077: es8316 driver causes kernel oops / panic on rockpro64
Processing control commands: > retitle -1 es8316 driver causes kernel oops / panic on rockpro64 Bug #1069077 [src:linux] rockpro64: multiple kernel oops and frequent boot failures Changed Bug title to 'es8316 driver causes kernel oops / panic on rockpro64' from 'rockpro64: multiple kernel oops and frequent boot failures'. -- 1069077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068770: marked as done (linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver)
Your message dated Mon, 15 Apr 2024 21:47:22 + with message-id and subject line Bug#1068770: fixed in linux 6.1.85-1 has caused the Debian Bug report #1068770, regarding linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver 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.) -- 1068770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: critical Tags: upstream security Justification: root security hole X-Debbugs-Cc: lw-deb-...@greyskydesigns.com, Debian Security Team Dear Maintainer, A Reddit thread[1] linked to a Github page[2] with a local root escalation exploit. This exploit works on the current "bookworm" stable kernel, 6.1.0-18-amd64. It can be worked around by blocking the n_gsm driver: echo 'blacklist n_gsm' | sudo tee -a /etc/modprobe.d/blacklist-gsm.conf sudo rmmod n_gsm [1] https://old.reddit.com/r/linux/comments/1c0i7tx/someone_found_a_kernel_0day/ [2] https://github.com/YuriiCrimson/ExploitGSM/ -- Package-specific info: ** Version: Linux version 6.1.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) ** Command line: BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.1.0-18-amd64 root=UUID=403bad0f-[snip] ro rootflags=subvol=@rootfs panic=5 ** Not tainted ** Kernel log: [2.783100] at24 0-0051: supply vcc not found, using dummy regulator [2.784137] at24 0-0051: 256 byte spd EEPROM, read-only [2.789726] usb 2-1.3: FTDI USB Serial Device converter now attached to ttyUSB1 [2.806774] ipmi_si: IPMI System Interface driver [2.810971] usbcore: registered new interface driver usbhid [2.811095] usbhid: USB HID core driver [2.811363] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS [2.811489] ipmi_platform: ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 1 irq 0 [2.811630] ipmi_si: Adding SMBIOS-specified kcs state machine [2.811813] ipmi_si IPI0001:00: ipmi_platform: probing via ACPI [2.812069] ipmi_si IPI0001:00: ipmi_platform: [io 0x0ca8] regsize 1 spacing 4 irq 0 [2.818248] ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state machine in favor of ACPI [2.818400] ipmi_si: Adding ACPI-specified kcs state machine [2.818581] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 0 [2.825415] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.0/0003:046B:FF10.0001/input/input3 [2.832623] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-:00:1a.0-1.5.1/input0 [2.832950] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.1/0003:046B:FF10.0002/input/input4 [2.834908] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-:00:1a.0-1.5.1/input1 [2.842988] ast :0a:00.0: vgaarb: deactivate vga console [2.844608] Console: switching to colour dummy device 80x25 [2.846274] ast :0a:00.0: [drm] Using P2A bridge for configuration [2.846281] ast :0a:00.0: [drm] AST 1100 detected [2.846293] ast :0a:00.0: [drm] Using analog VGA [2.846303] ast :0a:00.0: [drm] dram MCLK=204 Mhz type=0 bus_width=16 [2.850155] [drm] Initialized ast 0.1.0 20120228 for :0a:00.0 on minor 0 [2.855445] fbcon: astdrmfb (fb0) is primary device [2.896398] ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x0019fd, prod_id: 0x1588, dev_id: 0x20) [2.956975] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms ovfl timer [2.956979] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules [2.956980] RAPL PMU: hw unit of domain package 2^-16 Joules [2.962273] cfg80211: Loading compiled-in X.509 certificates for regulatory database [2.962515] cfg80211: Loaded X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf' [2.962782] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328' [2.963083] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [2.963382] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [2.964803] platform
Bug#1068675: marked as done (linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2))
Your message dated Mon, 15 Apr 2024 21:47:22 + with message-id and subject line Bug#1068675: fixed in linux 6.1.85-1 has caused the Debian Bug report #1068675, regarding linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) 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.) -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.82-1 Severity: normal Hi, Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64 leads to losing some SMART information, at least as queried by munin (in Debian 12) when it comes to sensors. I'm getting the following results on the 2 pairs of disks in this machine: - 2×ST4000VN008-2DR1 (sda, sdb) - 2×ST8000VN004-2M21 (sdc, sdd) root@anchorage:~# /usr/sbin/smartctl -A --nocheck=standby -d ata /dev/sda smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-19-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Device is in SLEEP mode, exit(2) For some reason, the “S.M.A.R.T values” graphs is still OK, while the “HDD temperature” graph (using the aforementioned command) isn't anymore. The “Device is in SLEEP mode” status getting reported is obviously a lie, since all disks are in use (one pair does system stuff, the other pair does media stuff). Rebooting a couple of time with this version gives consistent negative results. Rebooting into linux-image-6.1.0-18-amd64 gives data back. The trace that appears below seems to happen exactly once per boot (and not even once per disk). Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant -- Package-specific info: ** Version: Linux version 6.1.0-19-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.82-1 (2024-03-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-19-amd64 root=/dev/mapper/data-root ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: [ 23.726790] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 23.763253] EXT4-fs (dm-13): mounted filesystem with ordered data mode. Quota mode: none. [ 23.764773] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card0/input5 [ 23.765529] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card0/input6 [ 23.765566] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input7 [ 23.765595] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 23.765626] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 23.785394] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [ 23.786295] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 23.786473] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [ 23.798653] i915 :00:02.0: [drm] Cannot find any crtc or sizes [ 23.801990] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [ 23.823066] i915 :00:02.0: [drm] Cannot find any crtc or sizes [ 23.825531] i915 :00:02.0: [drm] Cannot find any crtc or sizes [ 23.916595] XFS (dm-4): Deprecated V4 format (crc=0) will not be supported after September 2030. [ 23.920456] EXT4-fs (dm-14): mounted filesystem with ordered data mode. Quota mode: none. [ 23.941160] XFS (dm-4): Mounting V4 Filesystem [ 24.076883] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Quota mode: none. [ 24.152240] XFS (dm-4): Ending clean mount [ 24.152258] xfs filesystem being mounted at /data/media supports timestamps until 2038 (0x7fff) [ 24.160691] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Quota mode: none. [ 24.177491] intel_rapl_common: Found RAPL domain package [ 24.177494] intel_rapl_common: Found RAPL domain core [ 24.177495] intel_rapl_common: Found RAPL domain uncore [ 24.177496] intel_rapl_common: Found RAPL domain dram [ 24.177500] intel_rapl_common: RAPL package-0 domain package locked by BIOS [ 24.177505] intel_rapl_common: RAPL package-0 domain dram locked by BIOS [ 24.415347] audit: type=1400 audit(1712616841.356:2): apparmor="STATUS" operation="profile_load" profile=&quo
Bug#1065320: marked as done (linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle)
Your message dated Mon, 15 Apr 2024 21:47:22 + with message-id and subject line Bug#1065320: fixed in linux 6.1.85-1 has caused the Debian Bug report #1065320, regarding linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle 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.) -- 1065320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: leeejobsacco...@mail.co.uk Dear Maintainer, * What led up to the situation? Trying to boot the system with the 6.1.0-18 kernel * What exactly did you do (or not do) that was effective (or ineffective)? I tried adding 'boot_delay=1000' boot option to slow the console scroll rate, to enable better recording of the error messages. I tried rebooting the previous 6.1.0-17 kernel. * What was the outcome of this action? After adding the 'boot_delay=1000' option the boot process progressed no further than "Loading initial ramdisk ..." (left for several minutes - required power cycle). The system boots sucessfully on the previous 6.1.0-17 kernel * What outcome did you expect instead? I expected the system to successfully boot. * Additional observations This system also normally includes 'hpet=disable' and 'acpi_enforce_resources=lax' boot options but removing these made no difference. Although I was not able to boot the system with the 'boot_delay=1000' option and obtain clear photographs of the console output - the ones I've attached suffer from 'overprinting' - it does seem clear that ACPI errors are being reported. There appear to be two distinct phases to this problem. Initially, ACPI seems to be reporting errors for "GPE", as shown in the first attached photograph, but after ~10 seconds or so, ACPI then switches to continuously reporting an error for PM_TIMER, as shown in the second attached photograph. At this point a power cycle is required. Purging and reinstalling the package made no difference. Atm, only three kernels are installed on this system but I have had more in the past as I normally compile my own kernels from the corresponding Debian source package. My own 6.1.76-1 kernel also suffers from the same problem, whereas my own 6.1.69-1 kernel boots and runs Ok. Comparing the kernel configs for 6.1.0-17 and 6.1.0-18 showed just one functional change - an additional Compile-time checks and compiler option, which did not seem relevant to this problem. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: E203NA product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: E203NA.312 board_vendor: ASUSTeK COMPUTER INC. board_name: E203NA board_version: 1.0 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [8086:5af0] (rev 0b) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 500 [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 12
Processed: tagging 1068675
Processing commands for cont...@bugs.debian.org: > tags 1068675 + pending Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Processing control commands: > forwarded -1 > https://lore.kernel.org/stable/20240410193207.qnb75osxuk4ov...@mraw.org/ Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Set Bug forwarded-to-address to 'https://lore.kernel.org/stable/20240410193207.qnb75osxuk4ov...@mraw.org/'. -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1068770 is grave
Processing commands for cont...@bugs.debian.org: > severity 1068770 grave Bug #1068770 [src:linux] linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver Severity set to 'grave' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1068770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068770: linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver
Processing control commands: > tags -1 + confirmed pending Bug #1068770 [src:linux] linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver Added tag(s) pending and confirmed. > found -1 6.1.82-1 Bug #1068770 [src:linux] linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver Marked as found in versions linux/6.1.82-1. -- 1068770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Processing control commands: > tags -1 + upstream Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Added tag(s) upstream. -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Processing control commands: > tags -1 - moreinfo Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Removed tag(s) moreinfo. > tags -1 + confirmed Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Added tag(s) confirmed. -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Processing control commands: > tags -1 + moreinfo Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Added tag(s) moreinfo. -- 1068675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1068356
Processing commands for cont...@bugs.debian.org: > close 1068356 Bug #1068356 [src:linux] linux-image-6.1.0-18-amd64: Debian 12.5 6.1.0-18-amd64 hibernate works the 1st time then "no space left on device" in journalctl Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1068356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1068020 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1068020 src:linux 6.6.15-2 Bug #1068020 [linux-image-amd64] Background process seemingly paused Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.6.15+2. Ignoring request to alter fixed versions of bug #1068020 to the same values previously set Bug #1068020 [src:linux] Background process seemingly paused Marked as found in versions linux/6.6.15-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1068020
Processing commands for cont...@bugs.debian.org: > tags 1068020 + moreinfo Bug #1068020 [src:linux] Background process seemingly paused Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1067858 to src:linux, found 1067858 in 6.1.82-1
Processing commands for cont...@bugs.debian.org: > reassign 1067858 src:linux 6.7.9-2 Bug #1067858 [src:linux-signed-amd64] reset SuperSpeed USB device number 2 using xhci_hcd Bug reassigned from package 'src:linux-signed-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.7.9+2 and linux-signed-amd64/6.1.82+1. Ignoring request to alter fixed versions of bug #1067858 to the same values previously set Bug #1067858 [src:linux] reset SuperSpeed USB device number 2 using xhci_hcd Marked as found in versions linux/6.7.9-2. > # accoring to reporter > found 1067858 6.1.82-1 Bug #1067858 [src:linux] reset SuperSpeed USB device number 2 using xhci_hcd Marked as found in versions linux/6.1.82-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1067033
Processing commands for cont...@bugs.debian.org: > close 1067033 Bug #1067033 [linux-image-amd64] linux-image-amd64: I want to chose capture yes or not in alsa Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1066883: alg: ecdh-nist-p256: test failed on vector 2, err=-14
Processing control commands: > tags -1 + moreinfo Bug #1066883 [src:linux] alg: ecdh-nist-p256: test failed on vector 2, err=-14 Added tag(s) moreinfo. -- 1066883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1061521 1066803
Processing commands for cont...@bugs.debian.org:
> forcemerge 1061521 1066803
Bug #1061521 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend
Bug #1064041 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-6.1.0-18-amd64: Resuming from suspend keyboard unresponsive (but
sysrq OK , touchpad OK) on dell latitude 3340
Bug #1064041 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-6.1.0-18-amd64: Resuming from suspend keyboard unresponsive (but
sysrq OK , touchpad OK) on dell latitude 3340
Marked as found in versions linux/5.10.209-2.
Ignoring request to alter found versions of bug #1061521 to the same values
previously set
Bug #1066803 [src:linux] linux-image-6.1.0-18-amd64: keyboard is not detected
after most recent security patch
Set Bug forwarded-to-address to
'https://lore.kernel.org/regressions/4eaf27ed-66a2-4aeb-a6b9-21e2b0455...@leemhuis.info/T/#ma73a2b47e9ecb7f4969f12b247cc48acb9c2e7d0
https://lore.kernel.org/stable/20240126160724.13278-1-hdego...@redhat.com/'.
Severity set to 'important' from 'critical'
Marked Bug as done
Marked as fixed in versions linux/6.1.82-1 and linux/6.7.4-1~exp1.
Marked as found in versions linux/5.10.209-2 and linux/6.6.13-1.
Added tag(s) moreinfo and upstream.
Merged 1061521 1064041 1066803
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521
1064041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064041
1066803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067006: marked as done (rpc-statd.service: State 'stop-sigterm' timed out. Killing.)
Your message dated Wed, 10 Apr 2024 09:00:17 +0200 with message-id and subject line Re: Bug#1067006: rpc-statd.service: State 'stop-sigterm' timed out. Killing. has caused the Debian Bug report #1067006, regarding rpc-statd.service: State 'stop-sigterm' timed out. Killing. 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.) -- 1067006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:2.6.4-3 Restarting rpc-statd.service (e.g via needrestart at upgrade time) runs into a timeout: Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State 'stop-sigterm' timed out. Killing. Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Killing process 2342 (rpc.statd) with signal SIGKILL. Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Main process exited, code=killed, status=9/KILL Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Failed with result 'timeout'. Mar 16 20:06:58 lola.afaics.de systemd[1]: Stopped rpc-statd.service - NFS status monitor for NFSv2/3 locking.. Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpcbind.service - RPC bind portmap service... Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpcbind.service - RPC bind portmap service. Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpc-statd.service - NFS status monitor for NFSv2/3 locking Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Version 2.6.4 starting Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Flags: TI-RPC Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpc-statd.service - NFS status monitor for NFSv2/3 locking.. Please reassign if necessary Regards Harri --- End Message --- --- Begin Message --- Hi Harald, On Sat, Mar 16, 2024 at 08:59:26PM +0100, Salvatore Bonaccorso wrote: > Hi, > > On Sat, Mar 16, 2024 at 08:13:44PM +0100, Harald Dunkel wrote: > > Package: nfs-common > > Version: 1:2.6.4-3 > > > > Restarting rpc-statd.service (e.g via needrestart at upgrade time) > > runs into a timeout: > > > > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State > > 'stop-sigterm' timed out. Killing. > > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Killing > > process 2342 (rpc.statd) with signal SIGKILL. > > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Main process > > exited, code=killed, status=9/KILL > > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Failed with > > result 'timeout'. > > Mar 16 20:06:58 lola.afaics.de systemd[1]: Stopped rpc-statd.service - NFS > > status monitor for NFSv2/3 locking.. > > Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpcbind.service - RPC > > bind portmap service... > > Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpcbind.service - RPC > > bind portmap service. > > Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpc-statd.service - NFS > > status monitor for NFSv2/3 locking > > Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Version 2.6.4 starting > > Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Flags: TI-RPC > > Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpc-statd.service - NFS > > status monitor for NFSv2/3 locking.. > > > > Please reassign if necessary > > I cannot reproduce this. If this was not a one-time off issue on your > system, do you have a way to reproduce the behaviour to further > investigate it? Closing it now as I'm not able to reproduce the issue. If you can please do reopen the bug without hesitation. Regards, Salvatore--- End Message ---
Processed: reassign 1067908 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1067908 src:linux Bug #1067908 [src:linux] Enable I6300ESB_WDT Ignoring request to reassign bug #1067908 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 1067908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1067908 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1067908 src:linux Bug #1067908 [linux-image-cloud-amd64] Enable I6300ESB_WDT Bug reassigned from package 'linux-image-cloud-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.1.76+1. Ignoring request to alter fixed versions of bug #1067908 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1067908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005960: marked as done (linux-image-5.15.0-0.bpo.3-amd64: Failed to boot due to "Failed to look up module alias 'autofs4': Function not implemented")
Your message dated Mon, 08 Apr 2024 22:20:19 -0700 with message-id <87sezvt8mk@debian-hx90.lan> and subject line Re: linux-image-5.15.0-0.bpo.3-amd64: Failed to boot due to "Failed to look up module alias 'autofs4': Function not implemented" has caused the Debian Bug report #1005960, regarding linux-image-5.15.0-0.bpo.3-amd64: Failed to boot due to "Failed to look up module alias 'autofs4': Function not implemented" 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.) -- 1005960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.15.15-2~bpo11+1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Booting with linux-image-5.15.0-0.bpo.3-amd64 fails and drops to root shell due to the following error message: [3.925863] systemd[1]: Failed to look up module alias 'autofs4': Function not implemented Boot using the linux-image-5.15.0-0.bpo.2-amd64 works. Will attach dmesg to help with debugging. If more information is needed please let me know. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: SYSTEM_MANUFACTURER product_name: HX90 product_version: Default string chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends International, LLC. bios_version: 5.19 board_vendor: Default string board_name: HX90 board_version: Default string ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport
Processed: Re: Bug#1068631: linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions
Processing control commands: > forcemerge -1 1054889 Bug #1068631 [src:linux] linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions Bug #1068631 [src:linux] linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions Marked as found in versions linux/6.5.6-1. Bug #1054889 [src:linux] linux-image-6.5.0-2-amd64: Kernel 6.5 amdgpu, with refreshrate above 120Hz, black screen appears when certain graphical element appear Marked as found in versions linux/6.6.15-2. Added tag(s) moreinfo. Merged 1054889 1068631 -- 1054889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054889 1068631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068631: linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions
Processing control commands: > tags -1 + moreinfo Bug #1068631 [src:linux] linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions Added tag(s) moreinfo. -- 1068631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: reset SuperSpeed USB device number 2 using xhci_hcd
Processing control commands: > found 1067858 6.1.82+1 Bug #1067858 [src:linux-signed-amd64] reset SuperSpeed USB device number 2 using xhci_hcd Marked as found in versions linux-signed-amd64/6.1.82+1. > notfound 1067858 6.1.76+1 Bug #1067858 [src:linux-signed-amd64] reset SuperSpeed USB device number 2 using xhci_hcd Ignoring request to alter found versions of bug #1067858 to the same values previously set > notfound 1067858 6.6.15+2 Bug #1067858 [src:linux-signed-amd64] reset SuperSpeed USB device number 2 using xhci_hcd Ignoring request to alter found versions of bug #1067858 to the same values previously set -- 1067858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067829: marked as done (nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We
Your message dated Sun, 07 Apr 2024 05:21:43 +
with message-id
and subject line Bug#1067829: fixed in nfs-utils 1:2.6.4-4
has caused the Debian Bug report #1067829,
regarding nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format
‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’
{aka ‘long long int’} [-Werror=format=]
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.)
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-utils
Version: 1:2.6.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=nfs-utils=armel=1%3A2.6.4-3%2Bb2=1711452552=0
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c xml.c -fPIC -DPIC -o .libs/xml.o
export-cache.c: In function ‘junction_flush_exports_cache’:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
| ~~^ ~~~
| | |
| | time_t {aka
long long int}
| long int
| %lld
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c display.c -o display.o >/dev/null 2>&1
cc1: some warnings being treated as errors
make[3]: *** [Makefile:489: export-cache.lo] Error 1
make[3]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.6.4-4
Done: Salvatore Bonaccorso
We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso (supplier of updated nfs-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Apr 2024 07:01:47 +0200
Source: nfs-utils
Architecture: source
Version: 1:2.6.4-4
Distribution: unstable
Urgency: mediu
Processed: bug 1067829 is forwarded to https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u
Processing commands for cont...@bugs.debian.org:
> forwarded 1067829
> https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Changed Bug forwarded-to-address to
'https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u' from
'https://bugzilla.kernel.org/show_bug.cgi?id=218540'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1067829
Processing commands for cont...@bugs.debian.org:
> tags 1067829 + confirmed pending
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1067829
Processing commands for cont...@bugs.debian.org:
> tags 1067829 + upstream
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Upgrade severity due to upload.
Processing commands for cont...@bugs.debian.org: > # OpenSSL 3.2 has been uploaded to unstable, raise the severity > severity 1061458 serious Bug #1061458 [src:gdm3] gdm3: Testsuite breaks with openssl 3.2 Severity set to 'serious' from 'important' > severity 1061869 serious Bug #1061869 [src:sssd] sssd: Drop -extensions from openssl command if there is no -x509. Severity set to 'serious' from 'important' > severity 1062235 serious Bug #1062235 [wireless-regdb] wireless-regdb: debci test fails with OpenSSL 3.2. Severity set to 'serious' from 'important' > severity 1063874 serious Bug #1063874 [m2crypto] m2crypto: Testsuite fails with OpenSSL 3.2 Severity set to 'serious' from 'important' > severity 1065529 serious Bug #1065529 [interimap] interimap: Testsuite fails with openssl 3.2 Severity set to 'serious' from 'important' > severity 1067532 serious Bug #1067532 [nagios-plugins-contrib] nagios-plugins-contrib: Testsuite fails with openssl 3.2 Severity set to 'serious' from 'important' > severity 1067572 serious Bug #1067572 [rust-parsec-tool] rust-parsec-tool: Testsuite fails with openssl 3.2 Severity set to 'serious' from 'important' > severity 1067636 serious Bug #1067636 [nodejs] nodejs: Testsuite fails with openssl 3.2 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1061458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061458 1061869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061869 1062235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062235 1063874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063874 1065529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065529 1067532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067532 1067572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067572 1067636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Having headers depend on image - bad idea I think
Processing control commands:
> reopen 1064976
Bug #1064976 {Done: Colm Buckley } [linux-headers-amd64]
linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding
linux-image-amd64 package
Bug reopened
Ignoring request to alter fixed versions of bug #1064976 to the same values
previously set
--
1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068189: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS
Processing control commands: > reassign -1 src:linux 6.7.9-2 Bug #1068189 [src:debhelper] debhelper: --link-doc checking for known packages makes linux-signed build FTBFS Bug reassigned from package 'src:debhelper' to 'src:linux'. No longer marked as found in versions debhelper/13.15. Ignoring request to alter fixed versions of bug #1068189 to the same values previously set Bug #1068189 [src:linux] debhelper: --link-doc checking for known packages makes linux-signed build FTBFS Marked as found in versions linux/6.7.9-2. -- 1068189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064976: marked as done (linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package)
Your message dated Mon, 1 Apr 2024 22:09:41 +0100 with message-id and subject line Re: Bug#1064976: linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package has caused the Debian Bug report #1064976, regarding linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package 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.) -- 1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-headers-6.6.13+bpo-amd64 Severity: normal X-Debbugs-Cc: c...@tuatha.org Dear Maintainer, The linux-headers packages for kernel version 6.6 seem to depend on the corresponding linux-image packages, but I believe that this should not be the case (and was not the case in previous versions). It should be possible to install the header files for a particular kernel version (eg: to allow for modules to be built for that version, which is my use case) without requiring the kernel image to be installed. I think the headers packages should depend on a suitable version of linux-kbuild and any necessary glibc headers or other build artifacts, but not on linux-image-* Many thanks, Colm -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'stable-security'), (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-headers-6.6.13+bpo-amd64 depends on: ii gcc-1212.2.0-14 pn linux-headers-6.6.13+bpo-common pn linux-image-6.6.13+bpo-amd64 | linux-image-6.6.13+bpo-amd64-unsi gned pn linux-kbuild-6.6.13+bpo linux-headers-6.6.13+bpo-amd64 recommends no packages. linux-headers-6.6.13+bpo-amd64 suggests no packages. --- End Message --- --- Begin Message --- With respect; this is not resolved. I fundamentally disagree with your assessment and with the approach of having a (largely) source package depend on a binary package. The extreme edge case (building BPF modules) should not dictate the general dependencies of the headers package; if necessary we can add linux-build-bpf-6.6 and similar which includes all necessary dependencies. There really has to be a way to install the headers Colm -- Colm Buckley | c...@tuatha.org On Mon, 1 Apr 2024 at 22:05, Colm Buckley wrote: > Sure - have a separate package which depends on a given version of both > (linux-complete-6.6.13-amd64?), but don't require the image to be installed > if all one needs is the headers. Or have the headers package "recommend" or > "suggest" the image package rather than depend on it. > > Consider, please, my use case - I can't imagine it's *that* unusual: I > have a build server which builds a bunch of DKMS modules for > numerous different kernel versions and architectures; at the moment it has > eight different headers packages installed, and builds modules and packages > them up into deb packages for each of these targets. If the image files for > all of these are pulled in also, that will be about 1GB of additional > churn, not to mention the additional work required to make sure my system > doesn't accidentally *boot* from one of these superfluous kernels; if it > boots from one of the -cloud-amd64 kernels for example, several important > hardware drivers will be missing. > > There are plenty of cases where the header files for a specific kernel > version might be needed but the image will be not merely useless, but > actively harmful (eg: small partition for /boot). > > The xz debacle over the weekend should serve as a warning against > overly-broad dependencies. Only depend on the things which the vast > majority of your users will need; building BPF modules is, with respect, a > severe edge case which should really be handled *specifically* rather than > being the *default*. > > Colm > > > > On Mon, 1 Apr 2024 at 21:35, Bastian Blank wrote: > >> On Mon, Mar 04, 2024 at 09:51:56AM +, Colm Buckley wrote: >> > As per the discu
Processed: reopen 1064976
Processing commands for cont...@bugs.debian.org:
> reopen 1064976
Bug #1064976 {Done: Bastian Blank } [linux-headers-amd64]
linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding
linux-image-amd64 package
Bug reopened
Ignoring request to alter fixed versions of bug #1064976 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1064976: marked as done (linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package)
Your message dated Mon, 1 Apr 2024 22:35:09 +0200 with message-id <20240401203509.xkfcptlougyfs...@shell.thinkmo.de> and subject line Re: Bug#1064976: linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package has caused the Debian Bug report #1064976, regarding linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package 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.) -- 1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-headers-6.6.13+bpo-amd64 Severity: normal X-Debbugs-Cc: c...@tuatha.org Dear Maintainer, The linux-headers packages for kernel version 6.6 seem to depend on the corresponding linux-image packages, but I believe that this should not be the case (and was not the case in previous versions). It should be possible to install the header files for a particular kernel version (eg: to allow for modules to be built for that version, which is my use case) without requiring the kernel image to be installed. I think the headers packages should depend on a suitable version of linux-kbuild and any necessary glibc headers or other build artifacts, but not on linux-image-* Many thanks, Colm -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'stable-security'), (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-headers-6.6.13+bpo-amd64 depends on: ii gcc-1212.2.0-14 pn linux-headers-6.6.13+bpo-common pn linux-image-6.6.13+bpo-amd64 | linux-image-6.6.13+bpo-amd64-unsi gned pn linux-kbuild-6.6.13+bpo linux-headers-6.6.13+bpo-amd64 recommends no packages. linux-headers-6.6.13+bpo-amd64 suggests no packages. --- End Message --- --- Begin Message --- On Mon, Mar 04, 2024 at 09:51:56AM +, Colm Buckley wrote: > As per the discussion in > https://salsa.debian.org/kernel-team/linux/-/merge_requests/1005 - once > vmlinux.h is included with linux-headers, the warning about cmd_btf_ko etc. > should be harmless, as that file should already be available (ie: there's > no need to generate it again as part of kernel build). Am I missing > something else? I confess I have only a very small amount of experience > with BPF code; I played with building a few modules, but I don't use it > regularly. No. We need to make sure someone installing linux-image-bla and linux-headers-bla have the same version, so the modules are compatible. vmlinux.h is not for modules. If you have a better idea how to solve this problem with kernel modules, please speak up. Bastian -- It is undignified for a woman to play servant to a man who is not hers. -- Spock, "Amok Time", stardate 3372.7--- End Message ---
Bug#1061445: marked as done (linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel)
Your message dated Mon, 1 Apr 2024 22:29:46 +0200 with message-id <20240401202946.6ceo6ecebrrwz...@shell.thinkmo.de> and subject line Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel has caused the Debian Bug report #1061445, regarding linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel 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.) -- 1061445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.7-cloud-amd64 Version: 6.6.13-1 Severity: normal Dear Debian folks, Trying to quickly start a VM, it’d be great to not use an initrd image, and also use the Virtio features, for example with the command below: qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 -device virtio-rng-pci -net nic,model=virtio-net-pci -net user,hostfwd=tcp::5-:22 -drive if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic Currently, that is not possible, as the driver is only available as module `virtio_blk.ko` (`CONFIG_VIRTIO_BLK=m`). It’d be great, if it could be built into the Linux kernel cloud image. Kind regards, Paul --- End Message --- --- Begin Message --- On Fri, Jan 26, 2024 at 01:44:44PM +0100, Paul Menzel wrote: > $ grep UUID /etc/default/grub > # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to > Linux > GRUB_DISABLE_LINUX_UUID=true > > I am now able to boot the VM image without an initrd, editing > `/boot/grub/grub.cfg`, which saves a little time, as the initrd does not > need to be loaded by GRUB and later dealt with (unpack/run) by the Linux > kernel. Sou you already have all the infrastructure to create initrd. Please use virtiofs for this case. Bastian -- Schshschshchsch. -- The Gorn, "Arena", stardate 3046.2--- End Message ---
Processed: Re: Bug#1064976: linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package
Processing control commands: > tags -1 wontfix Bug #1064976 [linux-headers-amd64] linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package Added tag(s) wontfix. -- 1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: linux-headers-amd64: linux-headers-* incorrectly depends on linux-image-*
Processing control commands: > tags -1 patch Bug #1064976 [linux-headers-amd64] linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package Added tag(s) patch. -- 1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1036884 with 1067272 1067494 1067829 1067561
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1067272 1067494 1067829 1067561 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1067193 1067171 1065787 1055530 1067190 1067509 1067189 1067458 1067069 1062847 1067288 1067677 1055352 1065973 1065816 1067192 1066049 1067676 1066794 1066328 1067170 1067508 1067175 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067272, 1067829, 1067494, and 1067561 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Wer
Processing control commands:
> tags -1 + patch
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) patch.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1067829 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=218540
Processing commands for cont...@bugs.debian.org:
> forwarded 1067829 https://bugzilla.kernel.org/show_bug.cgi?id=218540
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Set Bug forwarded-to-address to
'https://bugzilla.kernel.org/show_bug.cgi?id=218540'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1063338: marked as done (dlm: cannot start dlm midcomms -97)
Your message dated Thu, 28 Mar 2024 15:02:16 + with message-id and subject line Bug#1063338: fixed in linux 6.1.82-1 has caused the Debian Bug report #1063338, regarding dlm: cannot start dlm midcomms -97 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.) -- 1063338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-amd64 Version: 6.1.76+1 Source: linux Source-Version: 6.1.76+1 Severity: important Control: notfound -1 6.6.15-2 Dear Maintainers, We discovered a bug affecting dlm that prevents any tcp communications by dlm when booted with debian kernel 6.1.76-1. Dlm startup works (corosync-cpgtool shows the dlm:controld group with all expected nodes) but as soon as we try to add a lockspace dmesg shows: ``` dlm: Using TCP for communications dlm: cannot start dlm midcomms -97 ``` It seems that commit "dlm: use kernel_connect() and kernel_bind()" (e9cdebbe) was merged to 6.1. Checking the code it seems that the changed function dlm_tcp_listen_bind() fails with exit code 97 (EAFNOSUPPORT) It is called from dlm/lockspace.c: threads_start() -> dlm_midcomms_start() dlm/midcomms.c: dlm_midcomms_start() -> dlm_lowcomms_start() dlm/lowcomms.c: dlm_lowcomms_start() -> dlm_listen_for_all() -> dlm_proto_ops->listen_bind() = dlm_tcp_listen_bind() The error code is returned all the way to threads_start() where the error message is emmitted. Booting with the unsigned kernel from testing (6.6.15-2), which also contains this commit, works without issues. I'm not sure what additional changes are required to get this working or if rolling back this change is an option. We'd be happy to test patches that might fix this issue. Thanks for your help, Valentin --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.1.82-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Mar 2024 09:35:01 +0100 Source: linux Architecture: source Version: 6.1.82-1 Distribution: bookworm Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1024149 1056056 1061521 1063338 1063422 Changes: linux (6.1.82-1) bookworm; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.77 - asm-generic: make sparse happy with odd-sized put_unaligned_*() - [powerpc*] mm: Fix null-pointer dereference in pgtable_cache_add - [arm64] irq: set the correct node for VMAP stack - [arm64] drivers/perf: pmuv3: don't expose SW_INCR event in sysfs - [powerpc*] Fix build error due to is_valid_bugaddr() - [powerpc*] mm: Fix build failures due to arch_reserved_kernel_pages() - [x86] boot: Ignore NMIs during very early boot - [powerpc*] pmd_move_must_withdraw() is only needed for CONFIG_TRANSPARENT_HUGEPAGE - [powerpc*] lib: Validate size for vector operations - [x86*] mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel - perf/core: Fix narrow startup race when creating the perf nr_addr_filters sysfs file - debugobjects: Stop accessing objects after releasing hash bucket lock - regulator: core: Only increment use_count when enable_count changes - audit: Send netlink ACK before setting connection in auditd_set - ACPI: video: Add quirk for the Colorful X15 AT 23 Laptop - PNP: ACPI: fix fortify warning - ACPI: extlog: fix NULL pointer dereference check - ACPI: NUMA: Fix the logic of getting the fake_pxm value - PM / devfreq: Synchronize devfreq_monitor_[start/stop] - ACPI: APEI: set memory failure flags as MF_ACTION_REQUIRED on synchronous events - FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - UBSAN:
Bug#1063422: marked as done (linux-image-6.1.0-18-amd64: F2FS rw mount at boot fails with "invalid zstd compress level: 6")
Your message dated Thu, 28 Mar 2024 15:02:16 + with message-id and subject line Bug#1063422: fixed in linux 6.1.82-1 has caused the Debian Bug report #1063422, regarding linux-image-6.1.0-18-amd64: F2FS rw mount at boot fails with "invalid zstd compress level: 6" 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.) -- 1063422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrade to linux-image-6.1.0-18-amd64 6.1.76-1 F2FS filesystem fails to mount rw. Message in the boot journal: kernel: F2FS-fs (nvme0n1p6): invalid zstd compress level: 6 There was recently an f2fs patch to the 6.1 kernel tree which might be related: https://www.spinics.net/lists/stable-commits/msg329957.html Was able to recover the system by doing: sudo mount -o remount,rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,atgc,discard_unit=block,memory=normal /dev/nvme0n1p6 / under the running bad 6.1.0-18-amd64 kernel, then editing /etc/default/grub: GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, with Linux 6.1.0-17-amd64" and running 'update-grub' and rebooting to boot the 6.1.0-17-amd64 kernel. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Wyse 7040 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 1.20.0 board_vendor: Dell Inc. board_name: 0080PM board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [1028:0727] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Subsystem: Dell 6th-10th Gen Core Processor PCIe Controller (x16) [1028:0727] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:0727] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Dell 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [1028:0727] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31) Subsystem: Dell 100 Series/C230 Series Chipset Family Thermal Subsystem [1028:0727] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a
Bug#1064041: marked as done (linux-image-6.1.0-18-amd64: Resuming from suspend keyboard unresponsive (but sysrq OK , touchpad OK) on dell latitude 3340)
Your message dated Thu, 28 Mar 2024 15:02:16 + with message-id and subject line Bug#1061521: fixed in linux 6.1.82-1 has caused the Debian Bug report #1061521, regarding linux-image-6.1.0-18-amd64: Resuming from suspend keyboard unresponsive (but sysrq OK , touchpad OK) on dell latitude 3340 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.) -- 1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: important Tags: newcomer Dear Maintainer, After suspend on ram on my laptop (Dell latitude 3340), I can not anymore use the keyboard. In difference with bug #1061521 the touchpad is OK , the sysrq keys are OK. This problem does not exist with kernel 6.1.0-17 and appears with 6.1.0-18. To byspass this problem , I have edited the file /etc/default/grub to add the parameter atkbd.reset at the line GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet atkbd.reset" and executed the commande: sudo update-grub Regards Jacques -- Package-specific info: ** Version: Linux version 6.1.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-18-amd64 root=/dev/mapper/vgbruyere-root ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Latitude 3340 product_version: 01 chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A02 board_vendor: Dell Inc. board_name: 00NF02 board_version: A00 ** Loaded modules: rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_multiport ip6t_REJECT nf_reject_ipv6 xt_addrtype xt_LOG nf_log_syslog xt_nat ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc qrtr overlay cmac algif_hash algif_skcipher af_alg bnep lz4 lz4_compress zram zsmalloc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass binfmt_misc btusb btrtl ghash_clmulni_intel btbcm sha256_ssse3 uvcvideo btintel btmtk sha1_ssse3 videobuf2_vmalloc cdc_mbim videobuf2_memops videobuf2_v4l2 cdc_wdm bluetooth iwlmvm dell_laptop mei_hdcp snd_ctl_led cdc_ncm videobuf2_common mac80211 snd_hda_codec_realtek jitterentropy_rng snd_hda_codec_generic ledtrig_audio dell_smm_hwmon snd_hda_codec_hdmi cdc_ether sha512_ssse3 usbnet videodev libarc4 snd_hda_intel sha512_generic snd_intel_dspcfg aesni_intel mii mc dell_wmi snd_intel_sdw_acpi sparse_keymap qcserial iwlwifi ctr snd_hda_codec usb_wwan crypto_simd usbserial cryptd dell_smbios drbg snd_hda_core rapl dcdbas wmi_bmof intel_cstate snd_hwdep dell_wmi_descriptor snd_pcm iTCO_wdt ansi_cprng cfg80211 intel_uncore snd_timer intel_pmc_bxt mei_me iTCO_vendor_support mei snd watchdog ecdh_generic pcspkr ecc soundcore dell_smo8800 dell_rbtn ac rfkill joydev evdev sg serio_raw msr ecryptfs parport_pc ppdev lp parport fuse efi_pstore loop configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hid_logitech_hidpp dm_mod hid_logitech_dj sd_mod t10_pi hid_generic usbhid crc64_rocksoft crc64 hid crc_t10dif crct10dif_generic i915 ahci libahci drm_buddy i2c_algo_bit drm_display_helper libata cec rc_core sdhci_pci ttm xhci_pci cqhci scsi_mod xhci_hcd sdhci drm_kms_helper ehci_pci i2c_i801 ehci_hcd crct10dif_pclmul crct10dif_common crc32_pclmul usbcore drm psmouse crc32c_intel mmc_core e1000e lpc_ich i2c_smbus scsi_common usb_common battery video wmi button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Dell Haswell-ULT DRAM Controller [1028:061f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integr
Bug#1061521: marked as done (linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend)
Your message dated Thu, 28 Mar 2024 15:02:16 + with message-id and subject line Bug#1061521: fixed in linux 6.1.82-1 has caused the Debian Bug report #1061521, regarding linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend 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.) -- 1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.6.13-amd64 Version: 6.6.13-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: deb...@r2rien.net Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to the rescue, only power button. Stuck in gdm3 login screen, thus impossible to type password to unlock gnome-session I tagged it as grave so people with apt-listbugs could be informed -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (991, 'testing'), (990, 'unstable'), (600, 'stable'), (90, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.11-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-6.6.13-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod31-1 ii linux-base 4.9 Versions of packages linux-image-6.6.13-amd64 recommends: pn apparmor ii firmware-linux-free 20200122-2 Versions of packages linux-image-6.6.13-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.12-1 pn linux-doc-6.6 --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.1.82-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Mar 2024 09:35:01 +0100 Source: linux Architecture: source Version: 6.1.82-1 Distribution: bookworm Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1024149 1056056 1061521 1063338 1063422 Changes: linux (6.1.82-1) bookworm; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.77 - asm-generic: make sparse happy with odd-sized put_unaligned_*() - [powerpc*] mm: Fix null-pointer dereference in pgtable_cache_add - [arm64] irq: set the correct node for VMAP stack - [arm64] drivers/perf: pmuv3: don't expose SW_INCR event in sysfs - [powerpc*] Fix build error due to is_valid_bugaddr() - [powerpc*] mm: Fix build failures due to arch_reserved_kernel_pages() - [x86] boot: Ignore NMIs during very early boot - [powerpc*] pmd_move_must_withdraw() is only needed for CONFIG_TRANSPARENT_HUGEPAGE - [powerpc*] lib: Validate size for vector operations - [x86*] mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel - perf/core: Fix narrow startup race when creating the perf nr_addr_filters sysfs file - debugobjects: Stop accessing objects after releasing hash bucket lock - regulator: core: Only increment use_count when enable_count changes - audit: Send netlink ACK before setting connection in auditd_set - ACPI: video: Add quirk for the Colorful X15 AT 23 Laptop - PNP: ACPI: fix fortify warning - ACPI: extlog: fix NULL pointer dereference check - ACPI: NUMA: Fix the logic of getting the fake_pxm value - PM / devfreq: Synchronize devfreq_monitor_[start/stop] - ACPI: APEI: set memory failure flags as MF_ACTION_REQUIRED on synchronous events - FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree
Bug#1024149: marked as done (linux: CVE-2024-26621: 32-bit mmap() puts large files at non-random address)
Your message dated Thu, 28 Mar 2024 15:02:16 + with message-id and subject line Bug#1024149: fixed in linux 6.1.82-1 has caused the Debian Bug report #1024149, regarding linux: CVE-2024-26621: 32-bit mmap() puts large files at non-random address 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.) -- 1024149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.0.8-1 Tags: security Control: affects -1 + libc6 32-bit mmap() puts large (>= 2 MiB) files at the same address every time: $ i686-linux-gnu-gcc -static test-mmap.c -o test-mmap $ head -c $((2 * 1024 * 1024)) /dev/zero > zeros $ for i in 1 2 3; do ./test-mmap < zeros; done mmap(NULL, 2097152, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7c0 mmap(NULL, 2097152, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7c0 mmap(NULL, 2097152, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7c0 In contrast, for smaller files, there's a few bits of entropy in the address: $ head -c $((2 * 1024 * 1024 - 4096)) /dev/zero > zeros $ for i in 1 2 3; do ./test-mmap < zeros; done mmap(NULL, 2093056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7d4a000 mmap(NULL, 2093056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7db8000 mmap(NULL, 2093056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 0, 0) = 0xf7d99000 This weakens ASLR for most(?) programs, because libc.so.6 has recently become slightly larger than 2 MiB: $ wc -c /lib/i386-linux-gnu/libc.so.6 2225200 /lib/i386-linux-gnu/libc.so.6 $ for i in 1 2 3; do cat /proc/self/maps | grep ' r-xp .*/libc'; done f7c22000-f7d9b000 r-xp 00022000 fd:00 12059068 /lib/i386-linux-gnu/libc.so.6 f7c22000-f7d9b000 r-xp 00022000 fd:00 12059068 /lib/i386-linux-gnu/libc.so.6 f7c22000-f7d9b000 r-xp 00022000 fd:00 12059068 /lib/i386-linux-gnu/libc.so.6 Curiously, not all file systems are affected. I could reproduce the bug on ext4, but not on tmpfs or unionfs. -- Package-specific info: ** Version: Linux version 6.0.0-4-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-9) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.8-1 (2022-11-11) -- System Information: Debian Release: bookworm/sid APT prefers unstable Architecture: i386 (x86_64) Foreign Architectures: amd64 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.1.82-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Mar 2024 09:35:01 +0100 Source: linux Architecture: source Version: 6.1.82-1 Distribution: bookworm Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1024149 1056056 1061521 1063338 1063422 Changes: linux (6.1.82-1) bookworm; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.77 - asm-generic: make sparse happy with odd-sized put_unaligned_*() - [powerpc*] mm: Fix null-pointer dereference in pgtable_cache_add - [arm64] irq: set the correct node for VMAP stack - [arm64] drivers/perf: pmuv3: don't expose SW_INCR event in sysfs - [powerpc*] Fix build error due to is_valid_bugaddr() - [powerpc*] mm: Fix build failures due to arch_reserved_kernel_pages() - [x86] boot: Ignore NMIs during very early boot - [powerpc*] pmd_move_must_withdraw() is only needed for CONFIG_TRANSPARENT_HUGEPAGE - [powerpc*] lib: Validate size for vector operations - [x86*] mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel - perf/core: Fix narrow startup race when creating the perf
Bug#1053122: marked as done (linux-image-6.5.0-1-amd64: Kernel page fault in process exit due to bit flip)
Your message dated Fri, 22 Mar 2024 16:18:09 +0100 with message-id and subject line has caused the Debian Bug report #1053122, regarding linux-image-6.5.0-1-amd64: Kernel page fault in process exit due to bit flip 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.) -- 1053122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.5.3-1 Severity: important Tags: upstream X-Debbugs-Cc: frc.gabr...@gmail.com Dear Maintainer, First of all thanks for your hard work! I noticed my computer started freezing for few seconds when entering/exiting full screen videos in youtube using firefox and while trying to check if the issue also afected chromium I saw the following message in dmesg: [12569.564300] BUG: unable to handle page fault for address: 991989e936b8 [12569.564304] #PF: supervisor write access in kernel mode [12569.564306] #PF: error_code(0x0002) - not-present page [12569.564308] PGD 0 P4D 0 [12569.564311] Oops: 0002 [#1] PREEMPT SMP NOPTI [12569.564314] CPU: 10 PID: 328649 Comm: Chroot Helper Not tainted 6.5.0-1-amd64 #1 Debian 6.5.3-1 [12569.564317] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING WIFI II, BIOS 3205 08/14/2023 [12569.564318] RIP: 0010:down_write+0x23/0x70 [12569.564324] Code: 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 53 48 89 fb e8 2e bc ff ff bf 01 00 00 00 e8 74 3a 53 ff 31 c0 ba 01 00 00 00 48 0f b1 13 75 33 65 48 8b 04 25 80 29 03 00 48 89 43 08 bf 01 [12569.564326] RSP: 0018:a189d736fc70 EFLAGS: 00010246 [12569.564328] RAX: RBX: 991989e936b8 RCX: 891797aaef00 [12569.564330] RDX: 0001 RSI: 891989e645c0 RDI: 8e7c95dc [12569.564331] RBP: R08: 0060 R09: 80400014 [12569.564333] R10: 8918cbfeb7f8 R11: 0006 R12: 7f7e5fd0 [12569.564334] R13: 0001 R14: 891989e645c0 R15: 891989e64958 [12569.564336] FS: () GS:891c8ec8() knlGS: [12569.564338] CS: 0010 DS: ES: CR0: 80050033 [12569.564339] CR2: 991989e936b8 CR3: 0002c522 CR4: 00750ee0 [12569.564341] PKRU: 5554 [12569.564342] Call Trace: [12569.564345] [12569.564347] ? __die+0x23/0x70 [12569.564351] ? page_fault_oops+0x171/0x4f0 [12569.564354] ? srso_alias_return_thunk+0x5/0x7f [12569.564358] ? exc_page_fault+0x175/0x180 [12569.564362] ? asm_exc_page_fault+0x26/0x30 [12569.564367] ? down_write+0x1c/0x70 [12569.564370] ? down_write+0x23/0x70 [12569.564373] free_pgtables+0x1ba/0x1d0 [12569.564379] exit_mmap+0x141/0x310 [12569.564385] __mmput+0x3e/0x130 [12569.564389] do_exit+0x305/0xb20 [12569.564393] do_group_exit+0x31/0x80 [12569.564396] __x64_sys_exit_group+0x18/0x20 [12569.564398] do_syscall_64+0x60/0xc0 [12569.564401] ? preempt_count_add+0x4b/0xa0 [12569.564404] ? srso_alias_return_thunk+0x5/0x7f [12569.564407] ? up_read+0x3b/0x80 [12569.564410] ? srso_alias_return_thunk+0x5/0x7f [12569.564412] ? do_user_addr_fault+0x235/0x640 [12569.564415] ? srso_alias_return_thunk+0x5/0x7f [12569.564417] ? fpregs_assert_state_consistent+0x26/0x50 [12569.564419] ? srso_alias_return_thunk+0x5/0x7f [12569.564422] ? exit_to_user_mode_prepare+0x40/0x1d0 [12569.564425] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [12569.564428] RIP: 0033:0x7f7e9e6f1995 [12569.564430] Code: Unable to access opcode bytes at 0x7f7e9e6f196b. [12569.564432] RSP: 002b:7f7e798bd288 EFLAGS: 0206 ORIG_RAX: 00e7 [12569.564434] RAX: ffda RBX: 7f7e6aa5bee0 RCX: 7f7e9e6f1995 [12569.564435] RDX: 00e7 RSI: ff48 RDI: [12569.564437] RBP: 7f7e798bd298 R08: R09: [12569.564438] R10: 7f7e9e630178 R11: 0206 R12: 000b [12569.564440] R13: R14: 7f7e6aa5bee0 R15: 7f7e798bd560 [12569.56] [12569.564445] Modules linked in: uinput mptcp_diag xsk_diag tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag tls rfcomm nf_conntrack_netlink xfrm_user xfrm_algo snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nvme_fabrics ctr ccm qrtr overlay nfnetlink_log cmac lz4 lz4_compress algif_hash zram algif_skcipher zsmalloc af_alg bnep wireguard libchacha20poly1305 chacha_x86_64 poly1305_x86_64 curve25519_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nls_ascii nls_cp437 vfat fat nft_chain_nat xt_MASQUERADE nf_nat xt_addrtype
Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
Processing control commands: > reassign -1 tech-ctte Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely Bug reassigned from package 'linux-libc-dev' to 'tech-ctte'. No longer marked as found in versions linux/6.7.7-1. Ignoring request to alter fixed versions of bug #1065416 to the same values previously set > severity -1 normal Bug #1065416 [tech-ctte] linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely Severity set to 'normal' from 'serious' -- 1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1067228 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1067228 src:linux Bug #1067228 [linux-image-6.6.13+bpo-amd64-unsigned] linux-image-6.6.13+bpo-amd64-unsigned: _major_ cpu performance degradation from 6.1 Bug reassigned from package 'linux-image-6.6.13+bpo-amd64-unsigned' to 'src:linux'. Ignoring request to alter found versions of bug #1067228 to the same values previously set Ignoring request to alter fixed versions of bug #1067228 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1067228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
Processing control commands:
> reopen -1
Bug #1065416 {Done: Bastian Blank } [linux-libc-dev]
linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do
that completely
Bug reopened
Ignoring request to alter fixed versions of bug #1065416 to the same values
previously set
--
1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: cross-toolchain-base: Migrating linux-libc-dev
Processing control commands:
> unmerge 1059786
Bug #1059786 {Done: Bastian Blank } [linux-libc-dev]
cross-toolchain-base: Migrating linux-libc-dev
Bug #1065416 {Done: Bastian Blank } [linux-libc-dev]
linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do
that completely
Disconnected #1059786 from all other report(s).
> reassign 1059786 cross-toolchain-base
Bug #1059786 {Done: Bastian Blank } [linux-libc-dev]
cross-toolchain-base: Migrating linux-libc-dev
Bug reassigned from package 'linux-libc-dev' to 'cross-toolchain-base'.
No longer marked as found in versions linux/6.7.7-1.
Ignoring request to alter fixed versions of bug #1059786 to the same values
previously set
--
1059786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059786
1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1065416: marked as done (linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely)
Your message dated Wed, 20 Mar 2024 21:48:05 +0100 with message-id <20240320204805.i7qnygpujh6el...@shell.thinkmo.de> and subject line Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely has caused the Debian Bug report #1065416, regarding linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely 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.) -- 1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-libc-dev Version: 6.7.7-1 Severity: serious Tags: sid trixie linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely Provides: linux-libc-dev-amd64-cross (= 6.7.7-1), ... However the links in /usr/DEB_HOST_GNU_TYPE/include are missing. Please stop providing the cross-packages, you don't even need a breaks, because the current cross packages continue to work. Once that is done, I'll reduce the cross packages to some symlinks. --- End Message --- --- Begin Message --- Hi Not a single piece of evidence of a breakage showed up within the last weeks. I'm therefor closing this bug report. Regards, Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0--- End Message ---
Bug#1059786: marked as done (cross-toolchain-base: Migrating linux-libc-dev)
Your message dated Wed, 20 Mar 2024 21:48:05 +0100 with message-id <20240320204805.i7qnygpujh6el...@shell.thinkmo.de> and subject line Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely has caused the Debian Bug report #1065416, regarding cross-toolchain-base: Migrating linux-libc-dev 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.) -- 1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cross-toolchain-base Since Linux 6.6, the linux-libc-dev package in Debian is arch-all and includes headers in the appropriate multiarch include paths for all actually existing Debian architectures. Ubuntu also plans or already did that change as well. To finish this transition (which actually does not include any file conflicts), I intend to make changes to linux-libc-dev and - add Provides to any linux-libc-dev-*-cross in 6.7, - add Breaks to any linux-libc-dev-*-cross in 6.8. So after Linux 6.7 is in Trixie, you can remove building the linux-libc-dev-*-cross packages. Regards, Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9 --- End Message --- --- Begin Message --- Hi Not a single piece of evidence of a breakage showed up within the last weeks. I'm therefor closing this bug report. Regards, Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0--- End Message ---
Processed: reassign 1066826 to wnpp, reassign 1060763 to src:linux, reassign 1067054 to src:linux ...
: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067105 1067107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1067006
Processing commands for cont...@bugs.debian.org: > tags 1067006 + unreproducible Bug #1067006 [nfs-common] rpc-statd.service: State 'stop-sigterm' timed out. Killing. Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1066840: no mention of iproute2 6.7.0-2.1 in changelog
Processing control commands: > tags -1 wontfix Bug #1066840 [iproute2] no mention of iproute2 6.7.0-2.1 in changelog Added tag(s) wontfix. > close -1 Bug #1066840 [iproute2] no mention of iproute2 6.7.0-2.1 in changelog Marked Bug as done -- 1066840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063002: marked as done (iproute2: [INTL:it] Italian po-debconf translation update)
Your message dated Tue, 12 Mar 2024 23:39:06 + with message-id and subject line Bug#1063002: fixed in iproute2 6.8.0-1 has caused the Debian Bug report #1063002, regarding iproute2: [INTL:it] Italian po-debconf translation update 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.) -- 1063002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iproute2 Version: 6.7.0-2 Severity: wishlist Tags: l10n patch X-Debbugs-Cc: ce...@oziosi.org Hello, I updated the Italian po-debconf translation. The current one is attached. Cheers, -- Ceppo # iproute po-debconf italian translation. # Copyright (C) 2023, 2024 iproute2's copyright holder # This file is distributed under the same license as the iproute2 package. # Ceppo , 2023, 2024. # msgid "" msgstr "" "Project-Id-Version: iproute2\n" "Report-Msgid-Bugs-To: iprou...@packages.debian.org\n" "POT-Creation-Date: 2018-04-12 12:01+0100\n" "PO-Revision-Date: 2024-02-04 00:00+\n" "Last-Translator: Ceppo \n" "Language-Team: Italian \n" "Language: it\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "Allow ordinary users to run ip vrf exec using capabilities?" msgstr "" "Consentire agli utenti normali di eseguire ip vrf exec usando le capability?" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "iproute2 can be used to configure and use Virtual Routing and Forwarding " "(VRF) functionality in the kernel. This normally requires root permissions, " "but sometimes it's useful to allow ordinary users to execute commands from " "inside a virtual routing and forwarding domain. E.g. ip vrf exec examplevrf " "ping 10.0.0.1" msgstr "" "iproute2 può essere usato per configurare e utilizzare la funzionalità " "Virtual Routing and Forwarding (VRF) del kernel. Questo normalmente richiede " "i permessi di root, ma a volte è utile consentire agli utenti normali di " "eseguire comandi all'interno di un dominio virtuale di instradamento e " "inoltro. Ad esempio ip vrf exec examplevrf ping 10.0.0.1" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "The ip command supports dropping capabilities, making an exception for ip " "vrf exec. The drawback of setting the permissions is that if in the unlikely " "case of a security critical bug being found before the ip command has " "dropped capabilities then it could be used by an attacker to gain root " "permissions. It's up to you to decide about the trade-offs and select the " "best setting for your system. This will give cap_dac_override, cap_net_admin " "and cap_bpf to /bin/ip." msgstr "" "Il comando ip consente di invalidare le capability, ad eccezione di ip vrf " "exec. Lo svantaggio di impostare i permessi è che nell'improbabile caso che " "venga scoperto un bug di sicurezza critico prima che il comando ip abbia " "invalidato le capability esso potrebbe essere sfruttato da un attaccante per " "ottenere permessi di root. Bisogna valutare costi e benefici e selezionare " "le impostazioni migliori per il proprio sistema. Questo attribuirà " "cap_dac_override, cap_net_admin e cap_bpf a /bin/ip." #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "More information about VRF can be found at: https://www.kernel.org/doc/; "Documentation/networking/vrf.txt" msgstr "" "Più informazioni su VRF possono essere trovate a: https://www.kernel.org/doc/; "Documentation/networking/vrf.txt" --- End Message --- --- Begin Message --- Source: iproute2 Source-Version: 6.8.0-1 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of iproute2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian
Bug#1065214: marked as done (iproute2: recent libc6-dev change causes the RPC support to be dropped)
Your message dated Tue, 12 Mar 2024 23:39:06 + with message-id and subject line Bug#1065214: fixed in iproute2 6.8.0-1 has caused the Debian Bug report #1065214, regarding iproute2: recent libc6-dev change causes the RPC support to be dropped 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.) -- 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iproute2 Version: 6.7.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-gl...@lists.debian.org Usertags: libtirpc-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev, which depends on libtirpc-dev, has been added to the libc6-dev package. The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1 NMU, as part of the 64-bit time_t transition. This causes the RPC support in iproute2 (from misc/ss.c) to be dropped, I am not sure it is something to care about. Therefore please either: - Add libtirpc-dev as build dependency - Disable the RPC support explicitly using --without-rpc so that this feature does not depend on the packages installed on the system. Regards Aurelien --- End Message --- --- Begin Message --- Source: iproute2 Source-Version: 6.8.0-1 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of iproute2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated iproute2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Mar 2024 14:02:38 + Source: iproute2 Architecture: source Version: 6.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Luca Boccassi Closes: 1063002 1065214 Changes: iproute2 (6.8.0-1) unstable; urgency=medium . [ Ceppo ] * Update Italian po-debconf translation (Closes: #1063002) . [ Luca Boccassi ] * Add build dependency on libnsl-dev (Closes: #1065214) * Switch to pkgconf * Update upstream source from tag 'upstream/6.8.0' * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged upstream * Drop iproute2-doc package * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream Checksums-Sha1: 81308d7909eae86e194342cb35a987e4a868b1d7 2220 iproute2_6.8.0-1.dsc ae34022bef9a5270fd142bd42e4071d63ca9d575 913512 iproute2_6.8.0.orig.tar.xz 3d79726beb0f6e71acc39556253d1f6242b224bd 38776 iproute2_6.8.0-1.debian.tar.xz 44bbb6ffd43af2bc6da359f8f582d1814684dc21 7601 iproute2_6.8.0-1_source.buildinfo Checksums-Sha256: 414b27fd31535f3e52d410e07350bae481eb1e1d99a7e8c57374119178aaf9d1 2220 iproute2_6.8.0-1.dsc 03a6cca3d71a908d1f15f7b495be2b8fe851f941458dc4664900d7f45fcf68ce 913512 iproute2_6.8.0.orig.tar.xz 92a00d6e3e5910ee7d0a3a5518146a9d40df344394ddec20b0d1a0062d75188b 38776 iproute2_6.8.0-1.debian.tar.xz d92b2064a9bf3dae6eced327fe854fc488890505c25a1a98c7bd0405df10e1bc 7601 iproute2_6.8.0-1_source.buildinfo Files: e85257c0f00969eabe96ff9801c02325 2220 net optional iproute2_6.8.0-1.dsc 9d6ea453986900d98e3b6bcb868815cd 913512 net optional iproute2_6.8.0.orig.tar.xz 1678ebac3939af761b2b8a34f6f2a5e1 38776 net optional iproute2_6.8.0-1.debian.tar.xz 698e03cf6c0172b3119a6172f80e132d 7601 net optional iproute2_6.8.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmXw2kURHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB65FBAAvX2GxyKIA/nc9axUep1JkDdCe/f8jQQJ otVbxSHkX62vHP9REC6aAV81grann7USzihEXYwkjSV9pmyPn6tbMj/fZ3NkTEkx bTKMyewoL8qXjypu2hPJO3RBNdhmEbIrMT0cdXuDaFhVD70yvj3mYPXC2aCCYB0i d+bCjwoNhaK0QsfKBkX2c+h+jDQfjL6b2qud+DAzaoAxKAUJUu1+rJMZrUP1KrUa 3h1xE1FRS0WsJ1baz2L7BqtdCbtcHyRK1GMPa1eTrspYSrpS0nHb00jd1m+ft5gO rL8UREBF2zpTDGmr8Rb0NXdkiDV6+EQvLQzH80fJJmSP+adkuyogreq15EAZck/Y 6OVqDFvBYq5Hql9/QIytYP4HevembcjMHhPJDXrKDOeUMiK8q/oiHN/MVO/kUvb/ 38rjnMn8lTWoE586SjOY5HAWiec3o5xmhHhlUdO0EgjVr10Fv
Processed:
Processing control commands: > severity -1 wishlist Bug #1033663 [src:linux] linux: reproducible-builds: Embedded build path in various binaries Severity set to 'wishlist' from 'normal' -- 1033663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065214: marked as done (iproute2: recent libc6-dev change causes the RPC support to be dropped)
Your message dated Tue, 12 Mar 2024 08:43:12 + with message-id and subject line Bug#1065214: fixed in iproute2 6.7.0-2.1 has caused the Debian Bug report #1065214, regarding iproute2: recent libc6-dev change causes the RPC support to be dropped 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.) -- 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iproute2 Version: 6.7.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-gl...@lists.debian.org Usertags: libtirpc-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev, which depends on libtirpc-dev, has been added to the libc6-dev package. The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1 NMU, as part of the 64-bit time_t transition. This causes the RPC support in iproute2 (from misc/ss.c) to be dropped, I am not sure it is something to care about. Therefore please either: - Add libtirpc-dev as build dependency - Disable the RPC support explicitly using --without-rpc so that this feature does not depend on the packages installed on the system. Regards Aurelien --- End Message --- --- Begin Message --- Source: iproute2 Source-Version: 6.7.0-2.1 Done: Helmut Grohne We believe that the bug you reported is fixed in the latest version of iproute2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helmut Grohne (supplier of updated iproute2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Mar 2024 09:03:30 +0100 Source: iproute2 Architecture: source Version: 6.7.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Helmut Grohne Closes: 1065214 Changes: iproute2 (6.7.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Explicitly depend on libtirpc-dev. (Closes: #1065214) Checksums-Sha1: 351ecd7e3b21235742908eb0330074e112e31567 2266 iproute2_6.7.0-2.1.dsc bb0bd7b4e402c6d5b43b5983723610d94ea9cd4d 39872 iproute2_6.7.0-2.1.debian.tar.xz 8223b94ab099bcafcc2dd14873c8bb55e9fed280 7371 iproute2_6.7.0-2.1_amd64.buildinfo Checksums-Sha256: d41862f87536e500f5918120607c0641685f42ba99b4991cc8de997b64d7bca9 2266 iproute2_6.7.0-2.1.dsc b8d88b34daa3a6a12f6ec61bf304350f3e720dc316b6b7211cc45e6f26affce0 39872 iproute2_6.7.0-2.1.debian.tar.xz faa5a72dc096345faf8d94ca9dd71d245bd7666d80c128bb3b826854da985085 7371 iproute2_6.7.0-2.1_amd64.buildinfo Files: cea7117b3a7ec53120abbaca553ee307 2266 net optional iproute2_6.7.0-2.1.dsc 67b97450798c3b9024cc2f4211498074 39872 net optional iproute2_6.7.0-2.1.debian.tar.xz e3af4004054d38316bc6e1a6971de725 7371 net optional iproute2_6.7.0-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmXwDToACgkQLRqqzyRE REL7YBAApjwxVSyJRoB+j5hVkhLZN7d6NVb8cvk3aa/rMIyuAmYuzrWgDUhkEVid G56cSsjOuTW97EpYwcl1xrNGb9+fM1jLCtSQ2qhkGCLkkx1WCpBhfERxkM3wd6y/ e2ncCyThQVvlwlx7GkGc87gYKgSQMFOPxKCMip0HsOdAVNqkogU7eTdE9q6pgCbG Qiv55unGh/LsteXVaDDKhOUnkKKjHg954FSgLjiWoGQlBi/T5u1B/5iP3wsEB/8H wbMaanI7o/gALFFHlRxWoJ77qRp32dTeITYHJeiZ2fbL2e0//6aga7pE+F8G+U9E nk8WxWRHjfuf5ihVbngjssJ6YpQUezcVU5cdupynD/3cWhVbDGGRzY11nFjwThSQ ErY69MVXdy7qK67rji3r/H4Yb/jsKmdYgEKtHDw20BXxsZsYj51Deg40za+BcQRh Ypgud71rIcPL2fGduyZHJtNE/LKBpU7e7Z7cnWvI8q0jRFUgY2Udo4fxfg/G3ZZQ 9pQm1eEw3PwHUJ0pucqaNUi3oDwMZWxuoFeTiatVYju2AJ345e014Cxr8EsAFgfV sAt2Epx85pxCoDiTbpSzzSePJJ+RGjq+5qy9poPwU8V556fGgeOxMWmBfjFmWarw qS2LCJaJujef0O0UXeMJ/uY0UGwWeotXU3fkJifB5JPq+c4in8g= =jQSC -END PGP SIGNATURE- pgpQyPKaoiPOh.pgp Description: PGP signature --- End Message ---
Processed: NMU iproute2
Processing control commands: > tags -1 + pending Bug #1065214 [src:iproute2] iproute2: recent libc6-dev change causes the RPC support to be dropped Added tag(s) pending. -- 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1065819: linux-source-6.6 cannot be rebuild according to debian documentation
Processing control commands: > severity -1 important Bug #1065819 [linux-source-6.6] linux-source-6.6 cannot be rebuild according to debian documentation Severity set to 'important' from 'grave' -- 1065819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065320: marked as done (linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle)
Your message dated Sat, 09 Mar 2024 19:10:10 + with message-id and subject line Bug#1065320: fixed in linux 6.7.9-1 has caused the Debian Bug report #1065320, regarding linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle 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.) -- 1065320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: leeejobsacco...@mail.co.uk Dear Maintainer, * What led up to the situation? Trying to boot the system with the 6.1.0-18 kernel * What exactly did you do (or not do) that was effective (or ineffective)? I tried adding 'boot_delay=1000' boot option to slow the console scroll rate, to enable better recording of the error messages. I tried rebooting the previous 6.1.0-17 kernel. * What was the outcome of this action? After adding the 'boot_delay=1000' option the boot process progressed no further than "Loading initial ramdisk ..." (left for several minutes - required power cycle). The system boots sucessfully on the previous 6.1.0-17 kernel * What outcome did you expect instead? I expected the system to successfully boot. * Additional observations This system also normally includes 'hpet=disable' and 'acpi_enforce_resources=lax' boot options but removing these made no difference. Although I was not able to boot the system with the 'boot_delay=1000' option and obtain clear photographs of the console output - the ones I've attached suffer from 'overprinting' - it does seem clear that ACPI errors are being reported. There appear to be two distinct phases to this problem. Initially, ACPI seems to be reporting errors for "GPE", as shown in the first attached photograph, but after ~10 seconds or so, ACPI then switches to continuously reporting an error for PM_TIMER, as shown in the second attached photograph. At this point a power cycle is required. Purging and reinstalling the package made no difference. Atm, only three kernels are installed on this system but I have had more in the past as I normally compile my own kernels from the corresponding Debian source package. My own 6.1.76-1 kernel also suffers from the same problem, whereas my own 6.1.69-1 kernel boots and runs Ok. Comparing the kernel configs for 6.1.0-17 and 6.1.0-18 showed just one functional change - an additional Compile-time checks and compiler option, which did not seem relevant to this problem. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: E203NA product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: E203NA.312 board_vendor: ASUSTeK COMPUTER INC. board_name: E203NA board_version: 1.0 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [8086:5af0] (rev 0b) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 500 [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 12
