Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security
Control: tags -1 + moreinfo Hi David, On Sat, Sep 16, 2023 at 04:42:44PM -0300, David da Silva Polverari wrote: > Package: src:linux > Version: 6.1.52-1 > Severity: important > > Dear Maintainer(s), > > After upgrading the kernel from linux-image-6.1.0-11-amd64 (6.1.38-4) to > linux-image-6.1.0-12-amd64 (6.1.52-1) from bookworm-security on my > laptop (a Dell XPS 9560), the kernel fails to find the nvme disk, making > it impossible for the initrd to decrypt the drive using LUKS, and as > such there are no boot messages. On the previous kernel it boots fine. > With tha 6.1.0-12 kernel, dmesg shows the following: > > [ 42.074878] nvme nvme0: Does your device have a faulty power saving mode > enabled? > [ 42.074879] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 > pcie_aspm=off" and report a bug > [ 42.120786] nvme :04:00.0: Unable to change power state from D3cold to > D0, device inaccessible > [ 42.121007] nvme nvme0: Removing after probe failure status: -19 > [ 42.136737] nvme0n1: detected capacity change from 1000215216 to 0 > > When I tried using the suggested parameters, I could boot, boot soon > afterwards the system hung. I also tried some variations, as trying > either only nvm_core.default_ps_max_latency_us=0 or pcie_aspm=off, but > neither one worked. > > I attached the dmesg output from the laptop into this email. Can you verify if it's this issue known upstream? https://lore.kernel.org/regressions/5dhv0s.d0f751zf65...@gmail.com/ Does reverting the mentioned patch fix the issue? Regards, Salvatore
Processed: Re: Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security
Processing control commands: > tags -1 + moreinfo Bug #1052063 [src:linux] regression: nvme drive not found after kernel upgrade from bookworm-security Added tag(s) moreinfo. -- 1052063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security
Package: src:linux Version: 6.1.52-1 Severity: important Dear Maintainer(s), After upgrading the kernel from linux-image-6.1.0-11-amd64 (6.1.38-4) to linux-image-6.1.0-12-amd64 (6.1.52-1) from bookworm-security on my laptop (a Dell XPS 9560), the kernel fails to find the nvme disk, making it impossible for the initrd to decrypt the drive using LUKS, and as such there are no boot messages. On the previous kernel it boots fine. With tha 6.1.0-12 kernel, dmesg shows the following: [ 42.074878] nvme nvme0: Does your device have a faulty power saving mode enabled? [ 42.074879] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug [ 42.120786] nvme :04:00.0: Unable to change power state from D3cold to D0, device inaccessible [ 42.121007] nvme nvme0: Removing after probe failure status: -19 [ 42.136737] nvme0n1: detected capacity change from 1000215216 to 0 When I tried using the suggested parameters, I could boot, boot soon afterwards the system hung. I also tried some variations, as trying either only nvm_core.default_ps_max_latency_us=0 or pcie_aspm=off, but neither one worked. I attached the dmesg output from the laptop into this email. Regards, David [0.00] microcode: microcode updated early to revision 0xf4, date = 2023-02-23 [0.00] Linux version 6.1.0-12-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.52-1 (2023-09-07) [0.00] Command line: BOOT_IMAGE=/vmlinuz-6.1.0-12-amd64 root=/dev/mapper/mercurius--vg-root ro acpi_rev_override=1 mitigations=off quiet [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x6a305fff] usable [0.00] BIOS-e820: [mem 0x6a306000-0x6a306fff] ACPI NVS [0.00] BIOS-e820: [mem 0x6a307000-0x6a307fff] reserved [0.00] BIOS-e820: [mem 0x6a308000-0x7838dfff] usable [0.00] BIOS-e820: [mem 0x7838e000-0x7874afff] reserved [0.00] BIOS-e820: [mem 0x7874b000-0x78791fff] ACPI data [0.00] BIOS-e820: [mem 0x78792000-0x78e85fff] ACPI NVS [0.00] BIOS-e820: [mem 0x78e86000-0x7951] reserved [0.00] BIOS-e820: [mem 0x7952-0x795fefff] type 20 [0.00] BIOS-e820: [mem 0x795ff000-0x795f] usable [0.00] BIOS-e820: [mem 0x7960-0x7f7f] reserved [0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00047e7f] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.40 by American Megatrends [0.00] efi: ACPI=0x7875a000 ACPI 2.0=0x7875a000 SMBIOS=0x79367000 SMBIOS 3.0=0x79366000 TPMFinalLog=0x78b27000 ESRT=0x792bd198 MEMATTR=0x75be0018 MOKvar=0x79363000 [0.00] secureboot: Secure boot disabled [0.00] SMBIOS 3.0.0 present. [0.00] DMI: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.28.0 03/23/2022 [0.00] tsc: Detected 2800.000 MHz processor [0.00] tsc: Detected 2799.927 MHz TSC [0.000717] e820: update [mem 0x-0x0fff] usable ==> reserved [0.000720] e820: remove [mem 0x000a-0x000f] usable [0.000730] last_pfn = 0x47e800 max_arch_pfn = 0x4 [0.000844] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.001398] last_pfn = 0x79600 max_arch_pfn = 0x4 [0.009942] found SMP MP-table at [mem 0x000fced0-0x000fcedf] [0.009956] esrt: Reserving ESRT space from 0x792bd198 to 0x792bd1d0. [0.009966] Kernel/User page tables isolation: disabled on command line. [0.009967] Using GB pages for direct mapping [0.010344] RAMDISK: [mem 0x304b3000-0x34250fff] [0.010349] ACPI: Early table checksum verification disabled [0.010352] ACPI: RSDP 0x7875A000 24 (v02 DELL ) [0.010356] ACPI: XSDT 0x7875A0D0 00011C (v01 DELL CBX3 01072009 AMI 00010013) [0.010361] ACPI: FACP 0x7877FA78 00010C (v05 DELL CBX3 01072009 AMI 00010013) [0.010366] ACPI: DSDT 0x7875A278 0257FF (v02 DELL CBX3 01072009 INTL 20160422) [
iproute2_6.5.0-4_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Sep 2023 18:58:51 +0100 Source: iproute2 Architecture: source Version: 6.5.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Luca Boccassi Closes: 1051577 Changes: iproute2 (6.5.0-4) unstable; urgency=medium . * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS Checksums-Sha1: b9928c7fe0018926dc680275af54c3f1cb6a0c0f 2246 iproute2_6.5.0-4.dsc ae34769201655f6e6dc78fd8565cdd726a16ba9d 38208 iproute2_6.5.0-4.debian.tar.xz a58fb6d4de5721caa6e32bd09c905d7ccd07e4f7 7528 iproute2_6.5.0-4_source.buildinfo Checksums-Sha256: 0e714d3cea2375d80069eeda834988ad1374399a5f88bee6c083ef99a540cb35 2246 iproute2_6.5.0-4.dsc 22879801479d99d2b222aaa0f9b0feadba94af45fee1fc3ac53d1c01b5e8a177 38208 iproute2_6.5.0-4.debian.tar.xz a2e63a23f61cab0800124dc0df797177e77ac0f11274abe95cca7b168af93f01 7528 iproute2_6.5.0-4_source.buildinfo Files: f830f32f646178cf80215b72bb91f843 2246 net optional iproute2_6.5.0-4.dsc 3ed227ccdc72e03de6b245e14acafbe9 38208 net optional iproute2_6.5.0-4.debian.tar.xz 70f3c326bc99f36cb5538a7090911b6d 7528 net optional iproute2_6.5.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmUF950RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB7o6hAAzYTdzOXgkMIcXdzJ+AM5/TgMvkuDy1uQ Q1+vYeSeqSKQN6+LfEFGo6erAdh8WN4IQR2Xh5m48kvh2URSFkdHwfESf17rBYLm 92O0hc93kO2rD5rG9/tkV+maxds+xOPE0zd1+8SuYwOGTakzyQ0B2bm60oNrTiKJ HGH3ga3igRlfoHAjuNxn1BlZ5A65z98+GDNhgHZJ9RZUJTGOxdR5v8n1Z2Hbbsj0 +VwfrWRJ9Y5ZIsac0jG5IdaBf75ScMVZC1MYjlbZTdn/xR2dWTb/wMQghAAaomNV z3u/0n5r8ZjOYYRMOKTOTh3nj77H5r7FZInf7CPQ8h6Ci+1Tsw6R8em8jKGC1EMX eQv99SG5rENW0ZJE/BHQMnXW23kRBgmZS3dvLvv8fUFyabZ7IHkr/lJd3fbZS7mr 7NHr1zLHnltRv77bx0zXh9itmc5ypPrkQmGCszJMXVZFSEDlzQh9y2BtpvrIitic Xz6eaOTyv/G4LfTj0WidygBSiaPg/U4znILm/wsLn9OwNavCTHa9G9bA7GKwJk7I jFxc3gE/5Zf82bArklu54h8QUqFCqF00UlFYS1F/Roqruk2rpqK9zzs0d8Qex4pP Vk/4aD6KpVEXIwAGmQPBGABVcBV6bhE6ktbfNVF7jmUR2MK1xvwccq7z64NCZ839 +6rwdJeaOdI= =PYu1 -END PGP SIGNATURE-
Processed: reassign 1051467 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1051467 src:linux Bug #1051467 [s390/qeth] net: REGRESSION: relocating a Debian/bullseye guest is losing network connection Warning: Unknown package 's390/qeth' Bug reassigned from package 's390/qeth' to 'src:linux'. No longer marked as found in versions bullseye. Ignoring request to alter fixed versions of bug #1051467 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1051467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of iproute2_6.5.0-4_source.changes
iproute2_6.5.0-4_source.changes uploaded successfully to localhost along with the files: iproute2_6.5.0-4.dsc iproute2_6.5.0-4.debian.tar.xz iproute2_6.5.0-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1051577: marked as done (iproute2: obsolete conffiles)
Your message dated Sat, 16 Sep 2023 19:08:09 + with message-id and subject line Bug#1051577: fixed in iproute2 6.5.0-4 has caused the Debian Bug report #1051577, regarding iproute2: obsolete conffiles 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.) -- 1051577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iproute2 Version: 6.5.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After upgrading to 6.5.0-1 adequate shows: adequate found packaging bugs - - iproute2: obsolete-conffile /etc/iproute2/rt_tables.d/README iproute2: obsolete-conffile /etc/iproute2/rt_protos.d/README iproute2: obsolete-conffile /etc/iproute2/rt_protos iproute2: obsolete-conffile /etc/iproute2/rt_dsfield iproute2: obsolete-conffile /etc/iproute2/nl_protos iproute2: obsolete-conffile /etc/iproute2/ematch_map iproute2: obsolete-conffile /etc/iproute2/bpf_pinning Cf. dpkg-maintscript-helper(1) and dh_installdeb(1) / package.maintscript / rm_conffile. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmT898hfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZ76hAAvpluUC3obOOsJfmXhh48GqVoLEt/7wg2B7WR73f21nGSTMUP+nzDSE8W JwkGRIP8aT6eiHfh8zHj83Ey0r4IZ9g/OlMzyqCq7jDRzPo3fmy6Z3tJePGFO5Qg nYmZwQA9DA+ANUi0A9BqNvgofguXh9KxIk5k2Gd2M8P5OBPvcXuVBuXtARwPljVw 7wA+niYFUyjkL1rgj1eBdiwzzldyUJiGC4/cve2fkmQyXqtocTqWjQTEXa1zYRGn zRsCCyRdD0lJl/DqKTHspPyM/BAbWJbVnUPZ0Kn0LJAcvaUuOH+U4UAJTCshzaNM XzuAHx39Hh90SbRYvikASBPJX3s1jhOBTuJkH6qWjgtgQfSyElvujHqzOwUr73xX K5Ew9wDBAEbC5JDs4pLZGBQLUWmocQdAKRikPkScSqTpU+s/RIgwzg7uGsVK2tSo dO7zN6Q08NusJT6T4c7AYgSEHiLsH0rIHA7jY/x9roZ+X57Hg36YRGLdIL5UG74k 1dIgRZh4CpJZdmD28x5lW5Zk2oKE+x3GDhiZKuhoKJBSfH4CbNbHc3n4PkAIlBAD i2oxEkO20DwuJTiVmsQvDmYRWLOaSvA6Ffi02H78LQ3+QCFjXdKLIsm5Ex3wD7Me p+tSaEI4OE3VeaFY5xXnr20PIVe/7cf7TUAseyLB59vQk17tSIk= =dToJ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: iproute2 Source-Version: 6.5.0-4 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 1051...@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: Sat, 16 Sep 2023 18:58:51 +0100 Source: iproute2 Architecture: source Version: 6.5.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Luca Boccassi Closes: 1051577 Changes: iproute2 (6.5.0-4) unstable; urgency=medium . * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS Checksums-Sha1: b9928c7fe0018926dc680275af54c3f1cb6a0c0f 2246 iproute2_6.5.0-4.dsc ae34769201655f6e6dc78fd8565cdd726a16ba9d 38208 iproute2_6.5.0-4.debian.tar.xz a58fb6d4de5721caa6e32bd09c905d7ccd07e4f7 7528 iproute2_6.5.0-4_source.buildinfo Checksums-Sha256: 0e714d3cea2375d80069eeda834988ad1374399a5f88bee6c083ef99a540cb35 2246 iproute2_6.5.0-4.dsc 22879801479d99d2b222aaa0f9b0feadba94af45fee1fc3ac53d1c01b5e8a177 38208 iproute2_6.5.0-4.debian.tar.xz a2e63a23f61cab0800124dc0df797177e77ac0f11274abe95cca7b168af93f01 7528 iproute2_6.5.0-4_source.buildinfo Files: f830f32f646178cf80215b72bb91f843 2246 net optional iproute2_6.5.0-4.dsc 3ed227ccdc72e03de6b245e14acafbe9 38208 net optional iproute2_6.5.0-4.debian.tar.xz 70f3c326bc99f36cb5538a7090911b6d 7528 net optional iproute2_6.5.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmUF950RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB7o6hAAzYTdzOXgkMIcXdzJ+AM5/TgMvkuDy1uQ Q1+vYeSeqSKQN6+LfEFGo6erAdh8WN4IQR2Xh5m48kvh2URSFkdHwfESf17rBYLm
Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU
Hi, Am Sa den 16. Sep 2023 um 10:58 schrieb Bastian Blank: > On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote: > > Booting with the new kernel makes the display (1920x1200) heavily > > flckering, diplaying two times the same one above the other and only > > displaying about 1/4 of the screen smashed together on the left border > > of the screen. > > Does it work with native resolution? Does it work with Wayland? With the native resolution it works. And also with scaling. But it is hard to do the switch and the scaling. First due to the dsplaced display and second due to the tiny size. Thanks to xterm having font size Enormous. > > Note that the broken setup has 3 lines of 3840x2400, althogh I use > > 1920x1200 as resolution. > > With different refresh frequencies, so nothing uncommon. Well, yes, but not for a eDP, which has a single and only refresh rate. All others are broken and yould, in the worst case, destroy the display panel. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU
Am Sa den 16. Sep 2023 um 10:58 schrieb Bastian Blank: > On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote: > > Booting with the new kernel makes the display (1920x1200) heavily > > flckering, diplaying two times the same one above the other and only > > displaying about 1/4 of the screen smashed together on the left border > > of the screen. > > Does it work with native resolution? Does it work with Wayland? Well, I do not know about wayland as that never worked for me. And with native resolution, I don't think so but it is dificult to test as the display is so limited to select an other resolution. But I will try if I can handle that. > > Note that the broken setup has 3 lines of 3840x2400, althogh I use > > 1920x1200 as resolution. > > With different refresh frequencies, so nothing uncommon. True. Although that are the differences to the older and working kernel. > > 3840x2400 is no usable resolution as the display content is much to > > small to be usable. > > That's why we now have scaling and don't need to play with resolutions. Well, we had that discussion the last time to when it came out that it was a regression in kernel. It pretty much looks like this time again. And more over, the valid resolutions need to work. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1049332: marked as done (alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22))
Your message dated Sat, 16 Sep 2023 14:57:34 +0200 with message-id and subject line Re: Bug#1049332: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22) has caused the Debian Bug report #1049332, regarding alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22) 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.) -- 1049332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.4.4-3 Severity: normal X-Debbugs-Cc: in.cognit...@arcor.de Dear Maintainer, * What led up to the situation? Latest kernel update from Debian testing. * What exactly did you do (or not do) that was effective (or ineffective)? Latest kernel update from Debian testing. * What was the outcome of this action? Getting warnings and errors reported related to some RNG: [ 16.355099] sappc1 kernel: iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=6, TCOBASE=0x0400) [ 16.355328] sappc1 kernel: iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 16.357735] sappc1 kernel: DRBG: could not allocate digest TFM handle: hmac(sha512) [ 16.357739] sappc1 kernel: alg: drbg: Failed to reset rng [ 16.357740] sappc1 kernel: alg: drbg: Test 0 failed for drbg_nopr_hmac_sha512 [ 16.357741] sappc1 kernel: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22) [ 16.357743] sappc1 kernel: [ cut here ] [ 16.357744] sappc1 kernel: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22) [ 16.357751] sappc1 kernel: WARNING: CPU: 15 PID: 851 at crypto/testmgr.c:5936 alg_test+0x516/0x630 [ 16.357757] sappc1 kernel: Modules linked in: sha512_ssse3(+) mei_hdcp(+) mei_wdt(+) mei_pxp(+) sha512_generic iTCO_wdt intel_pmc_bxt snd_hwdep drbg(+) rapl iTCO_vendor_support pmt_telemetry joydev intel_cstate nft_redir cfg80211 watchdog intel_rapl_msr pmt_class snd_pcm intel_uncore snd_timer ansi_cprng mei_me wmi_bmof processor_thermal_device_pci snd pcspkr ecdh_generic(+) intel_lpss_pci processor_thermal_device ecc rfkill mei i2c_i801 intel_lpss soundcore thunderbolt(+) ucsi_acpi processor_thermal_rfim nft_chain_nat i2c_smbus idma64 processor_thermal_mbox typec_ucsi nf_nat processor_thermal_rapl roles intel_rapl_common intel_vsec typec int3403_thermal igen6_edac nf_conntrack i2c_hid_acpi i2c_hid button int340x_thermal_zone battery ac nf_defrag_ipv6 int3400_thermal intel_pmc_core acpi_pad nf_defrag_ipv4 acpi_thermal_rel nf_tables msr parport_pc ppdev lp parport nfnetlink fuse loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod efivarfs raid10 raid456 libcrc32c crc32c_generic [ 16.357799] sappc1 kernel: async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear md_mod hid_cherry hid_generic usbhid hid i915 i2c_algo_bit drm_buddy drm_display_helper drm_kms_helper cec rc_core crc32c_intel ttm nvme xhci_pci xhci_hcd nvme_core t10_pi drm usbcore aesni_intel psmouse evdev crypto_simd cryptd serio_raw crc64_rocksoft crc64 crc_t10dif crct10dif_generic usb_common crct10dif_pclmul crct10dif_common video wmi [ 16.357820] sappc1 kernel: CPU: 15 PID: 851 Comm: cryptomgr_test Tainted: G U 6.4.0-2-amd64 #1 Debian 6.4.4-3 [ 16.357823] sappc1 kernel: Hardware name: Framework Laptop (12th Gen Intel Core)/FRANMACP04, BIOS 03.05 08/23/2022 [ 16.357824] sappc1 kernel: RIP: 0010:alg_test+0x516/0x630 [ 16.357827] sappc1 kernel: Code: ff ff 4c 89 e6 4c 89 e7 41 89 c7 e8 24 fa fe ff e9 37 ff ff ff 44 89 f9 48 89 ea 4c 89 ee 48 c7 c7 d0 d9 ca 99 e8 4a f2 b5 ff <0f> 0b e9 7d fe ff ff 48 89 c2 48 89 ee 48 c7 c7 08 d9 ca 99 45 89 [ 16.357829] sappc1 kernel: RSP: :bce9c0b63e30 EFLAGS: 00010282 [ 16.357831] sappc1 kernel: RAX: RBX: RCX: [ 16.357832] sappc1 kernel: RDX: 0002 RSI: 0027 RDI: [ 16.357833] sappc1 kernel: RBP: 921b60dc7000 R08: R09: bce9c0b63cc0 [ 16.357834] sappc1 kernel: R10: 0003 R11: 9a2d26a8 R12: 0058 [ 16.357836] sappc1 kernel: R13: 921b60dc7080 R14: 0058 R15: ffea [ 16.357837] sappc1 kernel: FS: () GS:921edfbc() knlGS: [ 16.357838] sappc1 kernel:
Bug#1049332: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)
Control: tags -1 + unreproducible Hi, On Fri, Sep 15, 2023 at 06:21:02PM +0200, in.cognit...@arcor.de wrote: > Since reporting this issue I never got that error again in the journal. > > Feel free to close as "not reproducible". Thanks, to do some src:linux BTS housekeeping I following this closing this report. Regards, Salvatore
Processed: Re: Bug#1049332: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)
Processing control commands: > tags -1 + unreproducible Bug #1049332 [src:linux] alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22) Added tag(s) unreproducible. -- 1049332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1041745 to src:smartmontools, tagging 1041745 ...
Processing commands for cont...@bugs.debian.org: > reassign 1041745 src:smartmontools 7.3-1 Bug #1041745 [linux-image-6.1.0-10-amd64] smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Bug reassigned from package 'linux-image-6.1.0-10-amd64' to 'src:smartmontools'. No longer marked as found in versions linux-signed-amd64/6.1.38+1. Ignoring request to alter fixed versions of bug #1041745 to the same values previously set Bug #1041745 [src:smartmontools] smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Marked as found in versions smartmontools/7.3-1. > tags 1041745 + upstream Bug #1041745 [src:smartmontools] smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Added tag(s) upstream. > forwarded 1041745 https://www.smartmontools.org/ticket/1222 Bug #1041745 [src:smartmontools] smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Set Bug forwarded-to-address to 'https://www.smartmontools.org/ticket/1222'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU
Processing control commands: > tag -1 moreinfo Bug #1052006 [src:linux] linux-image-6.5.0-1-amd64 breaks X on amd GPU Added tag(s) moreinfo. -- 1052006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU
Control: tag -1 moreinfo Hi Klaus On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote: > Booting with the new kernel makes the display (1920x1200) heavily > flckering, diplaying two times the same one above the other and only > displaying about 1/4 of the screen smashed together on the left border > of the screen. Does it work with native resolution? Does it work with Wayland? > Note that the broken setup has 3 lines of 3840x2400, althogh I use > 1920x1200 as resolution. With different refresh frequencies, so nothing uncommon. > 3840x2400 is no usable resolution as the display content is much to > small to be usable. That's why we now have scaling and don't need to play with resolutions. Bastian -- The idea of male and female are universal constants. -- Kirk, "Metamorphosis", stardate 3219.8
Processed: reassign 1051592 to src:nftables, found 1051592 in 1.0.6-2+deb12u1, found 1051592 in 0.9.8-3.1 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1051592 src:nftables 1.0.6-2
Bug #1051592 [linux] linux: Regression - upgrade to 6.1.52-1 breaks nftables
Bug reassigned from package 'linux' to 'src:nftables'.
No longer marked as found in versions 5.10.191-1 and 6.1.52-1.
Ignoring request to alter fixed versions of bug #1051592 to the same values
previously set
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked as found in versions nftables/1.0.6-2.
> found 1051592 1.0.6-2+deb12u1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked as found in versions nftables/1.0.6-2+deb12u1.
> found 1051592 0.9.8-3.1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked as found in versions nftables/0.9.8-3.1.
> found 1051592 0.9.8-3.1+deb11u1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked as found in versions nftables/0.9.8-3.1+deb11u1.
> close 1051592 1.0.7-1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked as fixed in versions nftables/1.0.7-1.
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks
nftables
Marked Bug as done
> affects 1051592 + src:linux
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables]
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Added indication that 1051592 affects src:linux
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
