Processed: limit source to linux, tagging 1022848
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1022848 + pending Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Processing control commands: > severity -1 serious Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Severity set to 'serious' from 'important' -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Control: severity -1 serious Hi Christoph, Thanks for the quick feedback! On Thu, Oct 27, 2022 at 09:10:53PM +0200, Christoph Anton Mitterer wrote: > Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso > : > >According to your references there is the workaround of mounting with > >clear_cache,space_cache=v2 and convert the filesystem. > > > >What would one prevent doing so? > > v2 space cache is still rather new and had only recently some bug > that could have caused catastrophic data corruption... so not > everyone might want to switch. > > Similarly, people may want to have these filesystems mounted with > older kernels, whose v2 support isn't that good yet. Thanks, this is very important input. > >I'm downgrading the severity to important as it does not make the > >kernel unbootable or unstable on common hardware or all systems that a > >flavour is supposed to support. > > But now it a) migrates to testing an possibly leaves even more > systems with an unbootable system... b) with severity important, > people using e.g. apr-listbugs won't see it. > > OTOH, fixing the CVE is of course important, too. I did decide to still do so, so we can have the CVE fix migrate finally to testing (which took some time as well given there was the perl transition ongoing). I did import already 6.0.5 and will upload next so we get the btrfs fix. And I have made the bug now as well again back RC severity. Thank you! Regards, Salvatore
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: radeon v: kernel arch: GCN-1 pcie: speed: 2.5 GT/s lanes: 8 ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0 chip-ID: 1002:6611 Same failure as in my previous comment #45 about GCN2. In Bullseye in both PCs, workaround is to omit 'plymouth.enable=0 radeon.si_support=1' from linu line in Grub, which absent installation of radeon DDX, forces use of modesetting DIX instead of amdgpu DDX, which was working just fine until linux-image-5.10.0-19-amd64 was installed. The resulting change in display output names requires the xrandr script locating all the displays to be rewritten. On this one I've not as yet attempted installation of backport kernel. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#1022939: linux-image-6.0.0-2-amd64: 6.0.0-2-amd64 regressions: Lenovo Carbon X1 gen7 can't suspend, sound card not instantiated
Package: src:linux Version: 6.0.3-1 Severity: important X-Debbugs-Cc: d...@shallowsky.com Dear Maintainer, As of a sid full-upgrade two days ago (Tue Oct 25), I'm seeing two regressions on my Lenovo Carbon X1 gen7: - systemctl suspend no longer works: instead of suspending, it freezes, and I have to hold the power button for 10 seconds to force a power down - the laptop's built-in sound card (intel, using the firmware-intel-sound package) is no longer seen. In dmesg there's a "failed to instantiate card" error Both of these were working fine as of a system update a day or two earlier. The problem seem to be due to 6.0.0-2-amd64. If I reboot into my old kernel, 6.0.0-1-amd64, the sound card is found and suspend works. I hope it's not too presumptuous to put these both in the same error report; they seem very different but they happened at the same time and they're both cured by using the old kernel. For the suspend problem, I'm not sure how to debug a freeze or what additional info would be useful, but I'm happy to run any tests you suggest. For the sound card problem, pacmd list-sinks prints what seems to be a placeholder in the absence of finding an actual sound card (and the same for list-sources, it doesn't see the mic either): $ pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 1000 volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 375 KiB max rewind: 375 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms module: 11 properties: device.description = "Dummy Output" device.class = "abstract" device.icon_name = "audio-card" Here's the same command under 6.0.0-1-amd64 (where sound works): $ pacmd list-sinks 2 sink(s) available. index: 0 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9030 volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0.00 ms; range is 0.50 .. 341.33 ms module: 0 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "" alsa.id = "HDA Analog (*)" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "sof-hda-dsp" alsa.long_card_name = "LENOVO-20QDCTO1WW-ThinkPadX1Carbon7th" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9dc8" device.product.name = "Cannon Point-LP High Definition Audio Controller" device.string = "hw:0,0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "16384" device.access_mode = "mmap+timer" device.description = "Cannon Point-LP High Definition Audio Controller" device.icon_name = "audio-card-pci" * index: 1 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9030 volume: front-left: 64155 / 98% / -0.55 dB, front-right: 64155 / 98% / -0.55 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB
Bug#1022025: Fwd: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
On Sun, 23 Oct 2022 10:12:17 +0200 Michael Becker wrote: > 5.10.149-2 solved the problem 5.10.149-2 was no help with A10-7850K Radeon R7. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
On woensdag 26 oktober 2022 12:43:02 CEST Alexis Huxley wrote: > Following other reports of post-grub kernel hangs on systems with > amdgpu, I waited for new release of linux-image-5.10.0-19-amd64, > which came quickly, but it did not solve the problem for me. > > Symptoms are: grub loads kernel and a few seconds into the > scrolling messages from the kernel the system hangs. The screen > is blank. The system is not accessible over the network. AFAICT, which may be incorrect, the issue is slightly different from the other related bug report (#1022042) in that here it is a system which does not boot. The other problem that is fixed, is where the system does boot, but the graphics don't work correctly. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#105 is where Andreas Wirooks (See also https://gitlab.freedesktop.org/drm/amd/-/issues/ 2216#note_1601632) reported on that/this issue and in msg 110 'inasprecali' reported the same issue (AFAICT). See also the msgs that follow, which may give hints as to where the non-boot issue may come from. It _may_ also be related to older chipset variants. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Hi All, > Would you be able to start own kenel builds, confirming it does not > happen with 5.10.140 upstream but with 5.10.149, and isolate the > breaking change? > > (Are you able to boot the kernel from bullseye-backports?) I will try to do this, but owing to my schedule, it will be only Tuesday before I can try. If you did the kernel building and sent me download links then I can test them, which is obviously a lot less work for me, but a lot more for you. Otherwise I'll let you know how I get on next week. Sorry to have submitted tbe report and then immediatey not be available to do the followup. Regards, Alexis
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Hi Alexis, [Cc'ing Alex Deucher who addressed the previous regressions as well] On Wed, Oct 26, 2022 at 12:43:02PM +0200, Alexis Huxley wrote: > Package: src:linux > Version: 5.10.149-2 > Severity: serious > Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked > serious so this marked serious too > > Dear Maintainer, > > Following other reports of post-grub kernel hangs on systems with > amdgpu, I waited for new release of linux-image-5.10.0-19-amd64, > which came quickly, but it did not solve the problem for me. > > Symptoms are: grub loads kernel and a few seconds into the > scrolling messages from the kernel the system hangs. The screen > is blank. The system is not accessible over the network. > > I reverted to linux-image-5.10.0-18-amd64 and all is okay again. > > The crash happens pretty early on: I believe X has not yet tried > to start. Both /var/log/syslog and /var/log/messages contain > no entries pertaining to the hanging boot (only messages from > where the earlier shutdown of 18 and the later start of 18). > > Output from lscpu is below. > > Automatically included output (e.g. kernel version) pertains > to linux-image-5.10.0-18-amd64, as I am unable to boot > linux-image-5.10.0-19-amd64. I don't remove it in case it contains > other pertinent information. > > I'm happy to test with other kernels or provide any requested > files/output. Would you be able to start own kenel builds, confirming it does not happen with 5.10.140 upstream but with 5.10.149, and isolate the breaking change? (Are you able to boot the kernel from bullseye-backports?) Regards, Salvatore
Bug#1022806: Bug#1022025: fixed in linux 5.10.149-2
Hi, On Thu, Oct 27, 2022 at 07:12:43PM +, inasprecali wrote: > On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso > wrote: > > Can you please fill a new bug for your issue, which would still > > be > > present in the 5.10.149-2 release? There are two users which > > report > > that they still have problems with the amdgpu driver still in > > 5.10.149-2. > > I think bug 1022806 is a recent one referring to 5.10.149-2 > specifically, which is about this same issue. I don't think there > is a need to report yet another bug about it. Yes this is indeed enough. Regards, Salvatore
Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso : >According to your references there is the workaround of mounting with >clear_cache,space_cache=v2 and convert the filesystem. > >What would one prevent doing so? v2 space cache is still rather new and had only recently some bug that could have caused catastrophic data corruption... so not everyone might want to switch. Similarly, people may want to have these filesystems mounted with older kernels, whose v2 support isn't that good yet. >I'm downgrading the severity to important as it does not make the >kernel unbootable or unstable on common hardware or all systems that a >flavour is supposed to support. But now it a) migrates to testing an possibly leaves even more systems with an unbootable system... b) with severity important, people using e.g. apr-listbugs won't see it. OTOH, fixing the CVE is of course important, too. Cheers, Chris.
Processed: tagging 1022848
Processing commands for cont...@bugs.debian.org: > tags 1022848 + fixed-upstream Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso wrote: > Can you please fill a new bug for your issue, which would still > be > present in the 5.10.149-2 release? There are two users which > report > that they still have problems with the amdgpu driver still in > 5.10.149-2. I think bug 1022806 is a recent one referring to 5.10.149-2 specifically, which is about this same issue. I don't think there is a need to report yet another bug about it. Best regards. -- inasprecali
Bug#1022025: fixed in linux 5.10.149-2
Hi On Thu, Oct 27, 2022 at 05:21:32PM +, inasprecali wrote: > On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters > wrote: > > Source: linux > > Source-Version: 5.10.149-2 > > 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. > > I'm sorry, but your belief seems to be mistaken, since we have > multiple reports o 5.10.149-2 still not booting with the amdgpu > driver. Can you please fill a new bug for your issue, which would still be present in the 5.10.149-2 release? There are two users which report that they still have problems with the amdgpu driver still in 5.10.149-2. Thanks already, let's folloup there with some questions. Regards, Salvatore
Processed: Re: Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Processing control commands: > severity -1 important Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Severity set to 'important' from 'critical' -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Control: severity -1 important Hi, On Wed, Oct 26, 2022 at 10:23:35PM +0200, Christoph Anton Mitterer wrote: > Source: linux > Version: 5.19.6-1 > Severity: critical > Justification: breaks the whole system > > > Hi. > > 6.0.3 introduced a commit that causes (permanent) CPU soft lockups > for some people with btrfs filesystems, effectively breaking the > system, e.g. when booting. According to your references there is the workaround of mounting with clear_cache,space_cache=v2 and convert the filesystem. What would one prevent doing so? I'm downgrading the severity to important as it does not make the kernel unbootable or unstable on common hardware or all systems that a flavour is supposed to support. While I agree it is important to fix, this issue should not block the migration of the current kernel to address CVE-2022-2602. I will work next on importing the newer 6.0.y versions which include a fix for this issue as well. Regards, Salvatore
Processed: tagging 1022848
Processing commands for cont...@bugs.debian.org: > tags 1022848 + upstream Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022042: Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters wrote: > Source: linux > Source-Version: 5.10.149-2 > 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. I'm sorry, but your belief seems to be mistaken, since we have multiple reports o 5.10.149-2 still not booting with the amdgpu driver. Best regards. -- inasprecali
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
On Thursday, 27 October 2022 15:56:28 CEST Stephan Verbücheln wrote: > Version: 6.0.3-1 > > When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep > failing. With kernel 5.19.x it works on the same machine with the same > userland. Can you try whether applying the following patch fixes that issue? https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/? h=linux-6.0.y=c2a000ad03bb3a0d0f389adcfc9f8c61622da363 That is part of upstream's v6.0.4 tag/release. signature.asc Description: This is a digitally signed message part.
Bug#992304: Dell PowerEdge T140
Same problem with the Dell PowerEdge T140 with LSI MegaRAID SAS-3 3008 [Fury] (rev 02) and linux-image-5.10.0-19-amd64 (NO UEFI) No problem booting with the old 4.19.0-22-amd64 kernel
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Package: src:linux Version: 6.0.3-1 When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep failing. With kernel 5.19.x it works on the same machine with the same userland. Hardware: MacBookPro11,1, Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz I am not sure if this app is Apple specific. I recommend developers to test grub-install and efibootmgr on other hardware setups. grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi/EFI/debian/shimx64.efi'. grub-install: info: copying `/usr/lib/grub/x86_64-efi- signed/grubx64.efi.signed' -> `/boot/efi/EFI/debian/grubx64.efi'. grub-install: info: copying `/usr/lib/shim/mmx64.efi.signed' -> `/boot/efi/EFI/debian/mmx64.efi'. grub-install: info: copying `/usr/lib/shim/fbx64.efi.signed' -> `/boot/efi/EFI/debian/fbx64.efi'. grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' -> `/boot/efi/EFI/debian/BOOTX64.CSV'. grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' -> `/boot/efi/EFI/debian/grub.cfg'. grub-install: info: Registering with EFI: distributor = `debian', path = `\EFI\debian\shimx64.efi', ESP at hostdisk//dev/sda,gpt1. grub-install: info: executing modprobe efivars 2>/dev/null. grub-install: info: setting EFI variable Boot. grub-install: warning: Cannot set EFI variable Boot. grub-install: warning: efivarfs_set_variable: writing to fd 6 failed: Invalid argument. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Invalid argument. grub-install: error: failed to register the EFI boot entry: Invalid argument. Regards
Bug#1020534: marked as done (sgx: EPC section 0x50200000-0x55f7ffff (crash))
Your message dated Thu, 27 Oct 2022 14:38:11 +0200 with message-id <2663521.mvXUDI8C0e@bagend> and subject line Seems to be fixed has caused the Debian Bug report #1020534, regarding sgx: EPC section 0x5020-0x55f7 (crash) 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.) -- 1020534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 5.18.2-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since kernel 5.18.2-1 I'm getting the following error/message in dmesg: [0.465573] DMAR: Intel(R) Virtualization Technology for Directed I/O [0.465579] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.465581] software IO TLB: mapped [mem 0x49be6000-0x4dbe6000] (64MB) [0.465676] sgx: EPC section 0x5020-0x55f7 [0.466859] [ cut here ] [0.466863] WARNING: CPU: 1 PID: 55 at arch/x86/kernel/cpu/sgx/main.c:446 ksgxd+0x1b3/0x1c0 [0.466877] Modules linked in: [0.466881] CPU: 1 PID: 55 Comm: ksgxd Not tainted 5.18.0-1-amd64 #1 Debian 5.18.2-1 [0.466887] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET70W (1.55 ) 07/07/2022 [0.466889] RIP: 0010:ksgxd+0x1b3/0x1c0 [0.466896] Code: ff e9 f6 fe ff ff 48 89 df e8 99 dd 0c 00 84 c0 0f 84 c7 fe ff ff 31 ff e8 fa dd 0c 00 84 c0 0f 85 98 fe ff ff e9 b3 fe ff ff <0f> 0b e9 83 fe ff ff e8 a1 d8 90 00 90 0f 1f 44 00 00 41 57 48 c1 [0.466903] RSP: :b24640463ed8 EFLAGS: 00010283 [0.466913] RAX: b246403a1970 RBX: 9104c2753400 RCX: [0.466922] RDX: 8000 RSI: b246403a1930 RDI: [0.466925] RBP: 9104c1345300 R08: 9104c13456c0 R09: 9104c13456c0 [0.466928] R10: R11: 0001 R12: b24640073ce0 [0.466930] R13: 9104c2789980 R14: a0a5c1c0 R15: [0.466933] FS: () GS:91085168() knlGS: [0.466937] CS: 0010 DS: ES: CR0: 80050033 [0.466940] CR2: CR3: 00042d210001 CR4: 003706e0 [0.466943] DR0: DR1: DR2: [0.466945] DR3: DR6: fffe0ff0 DR7: 0400 [0.466948] Call Trace: [0.466952] [0.466956] ? _raw_spin_lock_irqsave+0x24/0x50 [0.466976] ? _raw_spin_unlock_irqrestore+0x23/0x40 [0.466982] ? __kthread_parkme+0x36/0x80 [0.466990] kthread+0xe8/0x110 [0.466994] ? kthread_complete_and_exit+0x20/0x20 [0.466998] ret_from_fork+0x22/0x30 [0.467008] [0.467010] ---[ end trace ]--- [0.468117] Initialise system trusted keyrings [0.468137] Key type blacklist registered [0.468217] workingset: timestamp_bits=36 max_order=22 bucket_order=0 [0.472438] zbud: loaded It does NOT occur with version 5.17.3-1 and 5.18-1~exp1, but it does occur with 5.18.2-1, 5.18.16-1, 5.19.6-1 and I first noticed it with a self-compiled 6.0-rc6 (custom branch based on Debian kernel's master branch). Where it does NOT occur, there is no message containing 'sgx' in dmesg at all and where it DOES occur it appears to be the same with only a variantion in line number with ``arch/x86/kernel/cpu/sgx/main.c`` There are 5 commits with 'sgx' in their primary commit message: diederik@prancing-pony:~/dev/kernel.org/linux$ git log --oneline v5.18..v5.18.2 | grep -ci sgx 5 And they are all sequential: $ git log --oneline 557b6a9ccceeec1ae13a83b4490458b92e064c0e..5aada654649d9bcf6b89d7c0d1ff4b794f9295d3 5aada654649d media: i2c: imx412: Fix reset GPIO polarity 22e83371210d x86/sgx: Ensure no data in PCMD page after truncate 0e1f97633953 x86/sgx: Fix race between reclaimer and page fault handler 69432ff18091 x86/sgx: Obtain backing storage page with enclave mutex held 876053dd7503 x86/sgx: Mark PCMD page as dirty when modifying contents 5ded81f42258 x86/sgx: Disconnect backing page references from dirty status 6ad9dbb202a9 HID: multitouch: add quirks to enable Lenovo X12 trackpoint But I haven't verified that the issue got introduced with one of them. No idea if it could be relevant, but the SGX related section in my BIOS has the following settings (on a Lenovo ThinkPad X1 Carbon 5th gen): Intel (R) SGX Control: Software Controlled Current State: Enabled (And an item to 'Change Owner EPOCH') I haven't changed those settings between reboots with the various kernels (or ever AFAIR). - --
Re: Bug#1012547: linux: disable user namespaces per default
Seems I'm not the only one who's quite concerned about the ongoing security impact of user namspaces, as the recent/current discussion about some LSM patches for 6.1 shows: 99% of all code does NOT WANT the user namespace thing, and it's been a big new attack surface for the kernel getting things subtly wrong. It's still a shame to see that Debian intentionally sacrifices the security of *all* users just for the needs of very few. I'd very much like to see where Linus gets his "99%" from. Sounds a like like a "I'm not using it, so 99% of all users aren't using it". Podman certainly supports and uses them, when run as non-root. [1] [2] The whole point of user namespaces is to *reduce* the attack surface, not increase it. If you don't have a comparable feature, you need to give your applications more power, increasing the risk of system compromise overall. For example: Running containers or container runtimes as root. That the implementation has serious issues like this one is sad, but it is more of an indication that the feature wasn't quite ready for general consumption yet, not that it's a bad feature per se. And how would you build a user base and discover issues without making the feature available to the general public? [1] https://medium.com/techbull/what-is-user-namespace-and-podmans-rootless-containers-fc4c292c6bad [2] https://opensource.com/article/18/12/podman-and-user-namespaces
Processed: notfound 924233 in 2.9.4-4, notfixed 998073 in 0.4.12-1, notfound 1004427 in 1:8.7p1-1 ...
Processing commands for cont...@bugs.debian.org:
> # unconfuse the BTS
> notfound 924233 2.9.4-4
Bug #924233 {Done: Andrej Shadura } [obs-server]
obs-server: fails to purge: delgroup: `obsservicerun' still has `obsrun' as
their primary group!
No longer marked as found in versions open-build-service/2.9.4-4.
> notfixed 998073 0.4.12-1
Bug #998073 [wireplumber] wireplumber: fails to automatically switch to
headphones when connected
No longer marked as fixed in versions 0.4.12-1.
> notfound 1004427 1:8.7p1-1
Bug #1004427 {Done: Colin Watson } [openssh-server]
openssh-server: Connection reset when trying to establish a connection on armhf
No longer marked as found in versions openssh/1:8.7p1-1.
> notfixed 1008997 2.4.1op1-2
Bug #1008997 {Done: Thorsten Alteholz } [cups] cups:
impossible to print on hp envy 5536 from sid
No longer marked as fixed in versions 2.4.1op1-2.
> found 1009636 2.0.0-1
Bug #1009636 [src:ruby-devise-two-factor] ruby-devise-two-factor:
CVE-2021-43177 - possible reuse of OTP due to incomplete fix for CVE-2015-7225
Marked as found in versions ruby-devise-two-factor/2.0.0-1.
> notfound 1009636 4.0.2-1
Bug #1009636 [src:ruby-devise-two-factor] ruby-devise-two-factor:
CVE-2021-43177 - possible reuse of OTP due to incomplete fix for CVE-2015-7225
No longer marked as found in versions ruby-devise-two-factor/4.0.2-1.
> notfixed 1018785 1:0.4.1-4
Bug #1018785 {Done: Torquil Macdonald Sørensen }
[python3-dolfinx-real] Problem with python3-dolfinx-real or libfftw3_mpi.so.3
No longer marked as fixed in versions 1:0.4.1-4.
> notfixed 1020863 4.4.4-1
Bug #1020863 {Done: Boyuan Yang <073p...@gmail.com>}
[src:python-flask-jwt-extended] python-flask-jwt-extended: Source-only upload
needed
No longer marked as fixed in versions 4.4.4-1.
> fixed 1020863 4.4.4-2
Bug #1020863 {Done: Boyuan Yang <073p...@gmail.com>}
[src:python-flask-jwt-extended] python-flask-jwt-extended: Source-only upload
needed
Marked as fixed in versions python-flask-jwt-extended/4.4.4-2.
> reopen 983913
Bug #983913 {Done: Debian FTP Masters }
[puppet-master,puppet-master-passenger] puppet-master,puppet-master-passenger:
depends on unavailable puppet-server
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 5.5.22-4+rm.
> fixed 979887 2021.08-1
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
There is no source info for the package 'lava' at version '2021.08-1' with
architecture ''
Unable to make a source version for version '2021.08-1'
Marked as fixed in versions 2021.08-1.
> notfixed 979887 2022.01.3-3
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
No longer marked as fixed in versions lava/2022.01.3-3.
> notfound 979887 2022.01.3-3
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
No longer marked as found in versions lava/2022.01.3-3.
> tags 979887 + sid bookworm
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
Added tag(s) sid and bookworm.
> found 979887 2021.01-1
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
There is no source info for the package 'lava' at version '2021.01-1' with
architecture ''
Unable to make a source version for version '2021.01-1'
Marked as found in versions 2021.01-1.
> reassign 1002548 indi-fli 1.5-1
Bug #1002548 {Done: Thorsten Alteholz } [libfli2,indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Bug reassigned from package 'libfli2,indi-fli' to 'indi-fli'.
No longer marked as found in versions indi-fli/1.5-1.
No longer marked as fixed in versions libfli/2.0-2, indi-fli/1.5-2, and
libfi/2.0-2.
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Marked as found in versions indi-fli/1.5-1.
> fixed 1002548 1.5-2
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Marked as fixed in versions indi-fli/1.5-2.
> affects 1002548 + libfli2
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Added indication that 1002548 affects libfli2
> reassign 1020504 src:linux 5.19.6-1
Bug #1020504 {Done: Salvatore Bonaccorso }
[linux-image-5.19.0-1-amd64] Bug on Debian 11 Bullseye - Kernel 5.19.6-amd64
dont run with Nvidia drivers
Warning: Unknown package 'linux-image-5.19.0-1-amd64'
Bug reassigned from package 'linux-image-5.19.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.19.6+1.
Ignoring request to alter fixed versions of bug #1020504 to the same values
previously set
Bug #1020504 {Done: Salvatore Bonaccorso } [src:linux] Bug
on Debian 11 Bullseye - Kernel 5.19.6-amd64 dont run
Bug#1022879:
Hi, This is my first bug report, so It seems that I've messed up the message body. So here it is: I've been experiencing several issues after upgrading my kernel to linux-image-6.0.0-2-amd64: * Suspend to ram no longer works. The screen just turns off, but the PC is still running. * The CPU runs much hotter. With Linux 5.19 it runs below 50 degrees, but with 6.0.0-2 it keeps around 55 degrees and the laptop is hot to the touch. * I cannot shut down or restart my PC - I have to hard-kill it by pressing the "power on/off" button. It just hangs on shutdown in "systemd-shutdown waiting for process (pid) modprobe". This DOES NOT happen with 5.19 Thanks and best regards, Svetlin
Bug#1022879: linux-image-6.0.0-2-amd64: Cannot suspend laptop after upgrade to linux-image-6.0.0-2-amd64
Package: src:linux Version: 6.0.3-1 Severity: normal X-Debbugs-Cc: je8bn1...@mozmail.com 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 *** -- Package-specific info: ** Version: Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-amd64 root=UUID=c0cf4120-1f35-4157-b077-2d2f5de04d62 ro quiet nmi_watchdog=0 mitigations=off ** Tainted: D (128) * kernel died recently, i.e. there was an OOPS or BUG ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20EGS0N01M product_version: ThinkPad W541 chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: GNET80WW (2.28 ) board_vendor: LENOVO board_name: 20EGS0N01M board_version: SDK0E50512 STD ** Loaded modules: ctr ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device nft_reject_ipv6 nf_reject_ipv6 overlay qrtr cmac algif_hash algif_skcipher cpufreq_userspace af_alg cpufreq_conservative bnep cpufreq_ondemand cpufreq_powersave nft_reject_ipv4 nf_reject_ipv4 intel_rapl_msr nft_reject intel_rapl_common binfmt_misc btusb btrtl btbcm btintel btmtk snd_ctl_led nft_ct bluetooth nf_conntrack snd_hda_codec_realtek snd_hda_codec_generic nf_defrag_ipv6 nf_defrag_ipv4 snd_hda_codec_hdmi x86_pkg_temp_thermal iwlmvm jitterentropy_rng uvcvideo intel_powerclamp snd_hda_intel snd_intel_dspcfg videobuf2_vmalloc sha512_ssse3 kvm_intel videobuf2_memops snd_intel_sdw_acpi mac80211 snd_hda_codec videobuf2_v4l2 libarc4 sha512_generic joydev snd_hda_core videobuf2_common mei_wdt mei_hdcp snd_hwdep iwlwifi kvm drbg videodev snd_pcm_oss irqbypass rapl ansi_cprng snd_mixer_oss iTCO_wdt intel_cstate snd_pcm thinkpad_acpi ecdh_generic intel_pmc_bxt mc rmi_smbus ecc intel_uncore iTCO_vendor_support mei_me snd_timer nvram rmi_core cfg80211 platform_profile at24 ledtrig_audio watchdog serio_raw pcspkr wmi_bmof mei snd soundcore rfkill ac evdev sg nf_tables coretemp msr parport_pc nfnetlink ppdev lp parport fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c crc32c_generic sd_mod t10_pi crc64_rocksoft_generic sr_mod crc64_rocksoft cdrom crc_t10dif crct10dif_generic crc64 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel i915 nouveau ghash_clmulni_intel mxm_wmi drm_buddy i2c_algo_bit drm_display_helper ahci libahci cec libata rc_core e1000e drm_ttm_helper ttm sdhci_pci drm_kms_helper xhci_pci cqhci ehci_pci ptp xhci_hcd scsi_mod sdhci aesni_intel ehci_hcd drm i2c_i801 mmc_core crypto_simd psmouse usbcore cryptd i2c_smbus lpc_ich scsi_common usb_common pps_core wmi battery video button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [17aa:2211] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [17aa:2211] 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 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] 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:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [17aa:2211]
linux-signed-i386_5.10.149+2_source.changes ACCEPTED into proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-i386 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-i386 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 2f12445864e6827eb474912d147a3d79e40e0ec7 14265 linux-signed-i386_5.10.149+2.dsc 9174d3ca6848820ea6b4bdedbb35366fb7920403 3747184 linux-signed-i386_5.10.149+2.tar.xz Checksums-Sha256: eabc88a923c24832423c23e420b4f409095c94f0c9c1f20190645bc3fb9c35bb 14265 linux-signed-i386_5.10.149+2.dsc a30f87fbf93840155a214ca566b91f6af8b24f137f6351dce8ff7db71527bf57 3747184 linux-signed-i386_5.10.149+2.tar.xz Files: eccac8665338955ceb0c4f66ed4dd4bd 14265 kernel optional linux-signed-i386_5.10.149+2.dsc 4a0d9d253c137a109a1f2a1b89e5b031 3747184 kernel optional linux-signed-i386_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNUlHQACgkQi0FRiLdO NzZhcQ/7BoK4TlyI+Im76291w9aTFNibbFxcqqbOt9hllMCuIcsuHVPJtpXUeLE0 ZmnWO36qK+g+4yPy1I/fxkKqiANyNMCIzeGrCweTFRSwBmk+6bqCSMWVJPj2v3aO /Oucr3h35/Zz/A4dL6xsk4g8uHmkalPVyMWKLeX/nEwDx8wa+lFDaXhK5alPFmRd k+NXPHUGf9dsflCNeHgMkJnoUowa7wStNABopVB0BVwmsu3d5SIM91DUYv8hCdYM TFIVxQpXr26vj6/qyo9ROGj1CazgRDcvhmhs+2Leb7N82Uwnog0jWsA3E4mn3D4X ptXnKZoBTjpvSr5UWa4RLxpNgyNyyRGanit/maJkReUWtAXdFrKHAV0sF4Lmmiod NOJe2ZANJjG201AWc7Qtax0PGbMR/gNkrPwb2puegVi17WMYJ1fAIUI4dWrdJ5ha duFS9mz2E2fO+myvyaPLvGgiW9m3uAlpo5cnTP3KWUATiFuNobUSNjgLqQSC5M4j mJwxWWrL+PgAL1FGg8t245EnoF5oB9pxcQh6M4AJlnRslmYpwur8EoClJU5NN5Ku S99118n5VHBc1ZpRyf8Y3/DW47NUcR0S7+Tmb+OUuy+TtkhbibMUAKkLb/sOh4W1 JsIHSvVtzAriztLkgoZKnOiniPGlTK3z28oiFfbKgoeCU4tUpQE= =Fgtq -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux-signed-arm64_5.10.149+2_source.changes ACCEPTED into proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-arm64 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 1f8029be2afa8259d1bd56524cee9aaca75e6a9f 7340 linux-signed-arm64_5.10.149+2.dsc 6dc0670584a776e52f2a9bebf5b993ad22f10774 2545540 linux-signed-arm64_5.10.149+2.tar.xz Checksums-Sha256: acf85af64c1cce1d8f0a63b0b2a26e05f293a913090d9f13da5a09e9f9addf3d 7340 linux-signed-arm64_5.10.149+2.dsc c204ea744399b89f34f9a96665e1fd4c59fad1fda072d9f16d6741f117b27de4 2545540 linux-signed-arm64_5.10.149+2.tar.xz Files: 2b9f17ccafbccbf12d1b1cdfc082dae6 7340 kernel optional linux-signed-arm64_5.10.149+2.dsc 8c68e85c862b3cfe4f795518f45be2ee 2545540 kernel optional linux-signed-arm64_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNT4eIACgkQi0FRiLdO NzZAFxAAoHQBzB4mB0ZhkPIOdSR9xxY0GVnxhL7b5eHElnByfDVtE1R26bBuGEDB JKEm5ErdlyhGLgJT+1MSd+P2/OH44187PPKaFSXIfXCibd5t6N0U4SZ7yknyrz28 grjolb2kdtTx5OB0Wip0Yn9Vyq2XSNEZeL/QW2hE0fzZCM73Uzs/5jEZK5vS3AuG CepdrYUi2nhmHNj3nJH23DgBHo4O74vo7QB80F6hisFkN6op+X2l0eqfQoJtKfyh /lErBATf3PECIs0t0eZVEA1WpBJBVbUj3pK9yQDo4D0tRJdZFKkfjcSsnuwUJ3Uh zAUGKRn5rVgr3Ot4chsfuR9+GukxCugLLWU0BctRwVPQ0mhga9wGXXLM3R1xdKdE 07VQMLQNDwYH3mX7f5Ik/LnJt0V3IauKjVeTJiK5o+AWyxVe1mQXzDCa7QCcnlbW GxJQ6VEZEjYTN4HRJskxwI20qQKESM6PGPkTcnvwwim41IZD/jLUsd7LLaJ95ztL z7SW1lDz8sWCL+y/b3eEOK47reb9k5Wk78kYoReRrVVP1bGyUH/nga8g8h7F9olO KmaqSJ11/fEj0x5msJzMyBHUB+ji1zJCA/wdKZe5mSUNEH8u+iKnZNeADdIcDOef +E3jy5sxE98NkPwfIxgbCtqEvjEGD4pjlSuiloEbtrl+3vWX3to= =2RUh -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux-signed-amd64_5.10.149+2_source.changes ACCEPTED into proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-amd64 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-amd64 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 55361c9e5a377b36a437298986461dfa4b66e6ca 8609 linux-signed-amd64_5.10.149+2.dsc 47706117437efee10024594a4af3d13a5e4d3d7c 2802384 linux-signed-amd64_5.10.149+2.tar.xz Checksums-Sha256: 00011ad99e9bf95fa411f595d8244c083611f6bf308453f02482d7db6e00b2cd 8609 linux-signed-amd64_5.10.149+2.dsc e626983c355796f2fbd76a2ecae39cabdbdddfd5935960a07a138a7d4dfad3be 2802384 linux-signed-amd64_5.10.149+2.tar.xz Files: 55f630c4b84817ccaa095d894dfce9b3 8609 kernel optional linux-signed-amd64_5.10.149+2.dsc 67f76ee1b0b0f11898ad45498b94619d 2802384 kernel optional linux-signed-amd64_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNTwZYACgkQi0FRiLdO NzZhiw/8CP2JT64MqhggaISk8uUxVGc69UFIbnehwHPU/FAj2cUdjR3PGpk23/UB Dc2oqwOxKlO85f2GayqUPMKIt3ubHO4dsyyp5nHIrlmigq/Q3v2sN9rH4VrWVRbp O+rg3T6rZnZ5vTSbWX6mQABGQrdHeZJgrEUKSDQmBjkQU4VtxOQnKJGscQJAfASM 0GUIqlV9MLTU0OXGQBiLMNvucs+EmCy1i7OfhD3pmklBau4pKWMrnMybjcyvKiJk 9o4mt4jBrhTz1XRm7B5jp8Tg3jEqFa3ep5PfkS4K8nY6USNsaPenbNoyx7PZlBN5 XtSFSPXpb31EnavyqZZavcgrXhCkhGmr0N9/w/4oQMZN40QS4WlvURypBw8/8eZ3 fkWWBV+N0WqEZaoWggu2VHcDJICRD1r+knMCQ8lcbAv+rzD5pBIX+yhX06GgqH8q DTdSmVY58c/oQFxo4l3ywKJiiVyJIsD3oPca/KYHgZsWxz7qQL9PzS3CHNHb4iKi 3i2J/Es5OgBBhlYvZdAB+xhOYu6FVwVp6Gxts9axYJnGmp2DxNKwt/kwZoXa/uMt fpDcWomcYbWPK8ujqdB1d9zi7AtoBIGuOeqy9QsVa8EZnGkXqylm8LBBFfeayH4H CWaWRyH7CPhITE8P63VYYeZx/kZhb/OspirKeYMkWyEcQXvwIxI= =uR7v -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux_5.10.149-2_source.changes ACCEPTED into proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux Architecture: source Version: 5.10.149-2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1022025 Changes: linux (5.10.149-2) bullseye-security; urgency=high . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 99ea79b0d9c39c38db9c74f1ef43fb92a65842a1 197238 linux_5.10.149-2.dsc 6aae804f7f39a4b87c6bb4568a626c4748798674 3473800 linux_5.10.149-2.debian.tar.xz 4791a4d12ca6778aefe2b8dfd25c3698d38030a4 6718 linux_5.10.149-2_source.buildinfo Checksums-Sha256: 3224be746cd8eb283471d0791ee1132b89bc0485e8c7348b9bce85f15852554e 197238 linux_5.10.149-2.dsc 2efe84aab6aeb700fd0a94f463b4a9f58f45f20e619e54841e962bb2bc03bab3 3473800 linux_5.10.149-2.debian.tar.xz 89916a1b5a0d8bc1ec8fc3be3ea0edccc2b5c5628021d8e2d87643c229b8c31f 6718 linux_5.10.149-2_source.buildinfo Files: e1988377a3b11f75ab8d6e88579d48a0 197238 kernel optional linux_5.10.149-2.dsc c07b55ab29e8a5e6d04233354412a958 3473800 kernel optional linux_5.10.149-2.debian.tar.xz 47eeb1ca50b368e2ed0232e82538460d 6718 kernel optional linux_5.10.149-2_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNTAFhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EPTQP/1iEL6iOJpv2OX7wf/l+xXi4s36VgJOU N3fZaRZwDT5oVyWl9A5WVXUR6P2U9t6hJCYI9idRVJ4DRyWTDDzlmOnFAiMCjRDl GoYpnls539pvG8JC7Q8gs5hPFckbARftSZamkxjIc0Y0s6poGG+SPqxTp/cnMBYU xWvURmFtCjjFTLwbl4Vb4GehoAk+ERfQDnSmQrYBauC2hO/0cP0UErypDd+FmuGr GZ2jahvigoRGGLsiJstTf15k/MHijnQSSvvFFCqXh/8Y2A0pdugXTd3feQoMbcFc 3eLXBvbkK4vAoQtIFnY1hqx3iFDs1CqdnBJ6ArEa4orCzYEfZ7/gNHowoAs4lwQa WFwyZDvV+gjMZgmDT87EA6UB7b11qQ8DrMzW81VCdM1y2PrZMCl+zmF4z05OX918 o3WE4AwURQ94W9JAqKsi4QNcHomzIErHtym3oH6Zv2tTVWKWz/XBLO7VNpwxcNJ6 h3FxCTePpI2cIZ04Ht46OZdtrhVWdeRF5/va6lUlL1pENdcRj2D4QfthLgQcBud6 PAozN+hky+ffcT2O/YR/Jz8Nz9tLXaW3fST8mP/Kl4awidGSXutbiqfq3WILIoS2 CnvBDA4I4OETBvpwOex1hWg44sedHofsJL0MKb62ozlOmuEyiKavTDW0UOP5b5vU U+Oz2wg9vkIj =GRlC -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1022070: marked as done (Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike)
Your message dated Thu, 27 Oct 2022 06:17:10 + with message-id and subject line Bug#1022025: fixed in linux 5.10.149-2 has caused the Debian Bug report #1022025, regarding Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike 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.) -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-5.10.0-19-amd64 Version: 5.10.149-1 Dear maintainer, This morning I upgraded my Lenovo Yoga 7 Series laptop with linux-image-5.10.0-19-amd64, and rebooted. Briefly after the initial RAM-disk was loaded, the screen was filling with errors, in a very (very) slow manner. The errors were like this: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out In /var/log/kern.log there seemed more to be found: Oct 19 15:49:55 yoga0 kernel: [ 976.653955] CPU: 10 PID: 336 Comm: plymouthd Tainted: G W 5.10.0-19-amd64 #1 Debian 5.10.149-1 Oct 19 15:49:55 yoga0 kernel: [ 976.653957] Hardware name: LENOVO 82CY/LNVNB161216, BIOS GHCN20WW 03/18/2021 Oct 19 15:49:55 yoga0 kernel: [ 976.654086] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu] Oct 19 15:49:55 yoga0 kernel: [ 976.654090] Code: a8 fd ff ff 01 c7 85 a4 fd ff ff 37 00 00 00 c7 85 ac fd ff ff 20 00 00 00 e8 9d 39 13 00 e9 f4 fa ff ff 0f 0b e9 5f f9 ff ff <0f> 0b e9 af f9 ff ff 0f 0b 0f 0b e9 c6 f9 ff ff 49 8b 06 41 0f b6 Oct 19 15:49:55 yoga0 kernel: [ 976.654092] RSP: 0018:ac03c0caf978 EFLAGS: 00010002 Oct 19 15:49:55 yoga0 kernel: [ 976.654094] RAX: 0002 RBX: e610 RCX: 89b240b48118 Oct 19 15:49:55 yoga0 kernel: [ 976.654096] RDX: 0001 RSI: 0297 RDI: 89b253960188 Oct 19 15:49:55 yoga0 kernel: [ 976.654097] RBP: ac03c0cafc70 R08: 0005 R09: Oct 19 15:49:55 yoga0 kernel: [ 976.654098] R10: ac03c0caf8d8 R11: ac03c0caf8dc R12: 0297 Oct 19 15:49:55 yoga0 kernel: [ 976.654099] R13: 89b240b48000 R14: 89b442aac800 R15: 89b24bf8d280 Oct 19 15:49:55 yoga0 kernel: [ 976.654101] FS: 7fbdf4fce740() GS:89b53e68() knlGS: Oct 19 15:49:55 yoga0 kernel: [ 976.654103] CS: 0010 DS: ES: CR0: 80050033 Oct 19 15:49:55 yoga0 kernel: [ 976.654104] CR2: 5623fe743058 CR3: 0001203ac000 CR4: 00750ee0 Oct 19 15:49:55 yoga0 kernel: [ 976.654105] PKRU: 5554 Oct 19 15:49:55 yoga0 kernel: [ 976.654106] Call Trace: Oct 19 15:49:55 yoga0 kernel: [ 976.654123] ? vprintk_emit+0x171/0x260 Oct 19 15:49:55 yoga0 kernel: [ 976.654130] ? printk+0x58/0x73 Oct 19 15:49:55 yoga0 kernel: [ 976.654143] ? drm_atomic_helper_wait_for_dependencies+0x1e4/0x200 [drm_kms_helper] Oct 19 15:49:55 yoga0 kernel: [ 976.654167] ? __drm_err+0x72/0x90 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654179] commit_tail+0x94/0x130 [drm_kms_helper] Oct 19 15:49:55 yoga0 kernel: [ 976.654191] drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper] Oct 19 15:49:55 yoga0 kernel: [ 976.654202] drm_atomic_helper_dirtyfb+0x188/0x260 [drm_kms_helper] Oct 19 15:49:55 yoga0 kernel: [ 976.654224] drm_mode_dirtyfb_ioctl+0xfc/0x1d0 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654244] ? drm_mode_getfb2_ioctl+0x2d0/0x2d0 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654260] drm_ioctl_kernel+0xae/0x100 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654276] drm_ioctl+0x224/0x3c0 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654292] ? drm_mode_getfb2_ioctl+0x2d0/0x2d0 [drm] Oct 19 15:49:55 yoga0 kernel: [ 976.654348] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Oct 19 15:49:55 yoga0 kernel: [ 976.654353] __x64_sys_ioctl+0x8b/0xc0 Oct 19 15:49:55 yoga0 kernel: [ 976.654357] do_syscall_64+0x33/0x80 Oct 19 15:49:55 yoga0 kernel: [ 976.654360] entry_SYSCALL_64_after_hwframe+0x61/0xc6 Oct 19 15:49:55 yoga0 kernel: [ 976.654361] RIP: 0033:0x7fbdf52596b7 Oct 19 15:49:55 yoga0 kernel: [ 976.654364] Code: 00 00 00 48 8b 05 d9 c7 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 c7 0d 00 f7 d8 64 89 01 48 Oct 19 15:49:55 yoga0 kernel: [ 976.654364] RSP:
Bug#1022062: marked as done (regression on amdgpu: drm_kms_helper "flip_done timed out" messages during boot and console freeze)
Your message dated Thu, 27 Oct 2022 06:17:10 + with message-id and subject line Bug#1022025: fixed in linux 5.10.149-2 has caused the Debian Bug report #1022025, regarding regression on amdgpu: drm_kms_helper "flip_done timed out" messages during boot and console freeze 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.) -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-5.10.0-19-rt-amd64 Severity: important X-Debbugs-Cc: jhlei...@gmail.com Dear Maintainer, linux-image-5.10.0-19-rt-amd64 drm_kms_helper "flip_done timed out" messages during boot. amdgpu. Only "nomodeset" works. This started upgrading from vunerable linux-image-5.10.0-18-rt-amd64 to linux-image-5.10.0-19-rt-amd64 (Debian security). I see a constant stream of these messages which repeat: [ 16.405686] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 26.645844] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 36.885904] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out I see a Linux Mint user has the same problem with 5.10.0.19-amd64 that I have ( https://forums.linuxmint.com/viewtopic.php?t=383942=2247003 ). I have an amdgpu. Hardware name: ASUS System Product Name/PRIME B550M-K, BIOS 2803 04/28/2022 (This motherboard has the AMD B550 chipset. I already installed the most recent BIOS version for this motherboard.) CPU model name: AMD Ryzen 7 5700G with Radeon Graphics microcode : 0xa5d cpu MHz : 1516.675 The system is not completely dead. I can ssh into it from another computer. My daemons like apache,squid and apt-cacher-ng are responsive. The problem is I do not have **any** VTs and lightdm never appears on VT7. Thinking that the "rt" version was fussy about hardware, I tried linux-image-5.10.0-19-amd64 but had the same poor results. I tried some suggestions I found on the internet: I changed from GRUB_CMDLINE_LINUX_DEFAULT="quiet" to GRUB_CMDLINE_LINUX_DEFAULT="quiet video=SVIDEO-1:d" I changed GRUB_CMDLINE_LINUX="zswap.enabled=1 blacklist=watchdog,sp5100_tco" to GRUB_CMDLINE_LINUX="amd_iommu=on iommu=pt amdgpu.noretry=0 amdgpu.lockup_timeout=1000 amdgpu.gpu_recovery=1 amdgpu.audio=0 efi=runtime zswap.enabled=1 blacklist=watchdog,sp5100_tco" These parameter changes did not help. The only way I successfully boot is to either use the vunerable linux-image-5.10.0-18-rt-amd64 or use GRUB_CMDLINE_LINUX="nomodeset zswap.enabled=1 blacklist=watchdog,sp5100_tco" The GUI resolution with "nomodeset" is poor. Please let me know if you need more information. dmesg gives much more context: [ 16.405686] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 16.407440] amdgpu :0a:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 16.437782] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [ 16.437786] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 16.437787] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 16.437788] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 16.437789] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 16.437789] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 16.437790] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 16.437791] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 16.437791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 16.437792] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 16.437793] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [ 16.437794] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [ 16.437795] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [ 16.437796] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [ 16.437797] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [ 16.443571] [drm] Initialized amdgpu 3.40.0 20150101 for :0a:00.0 on minor 0 [ 26.645844] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 36.885904]
Bug#1022051: marked as done (linux-image-5.10.0-19-amd64: no boot possible)
Your message dated Thu, 27 Oct 2022 06:17:10 + with message-id and subject line Bug#1022025: fixed in linux 5.10.149-2 has caused the Debian Bug report #1022025, regarding linux-image-5.10.0-19-amd64: no boot possible 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.) -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.149-1 Severity: critical Justification: breaks the whole system 5.10.0-18 works without problems the problem starts with the error: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out this part of the journal might help: Okt 19 16:00:16 hiltrup kernel: [ cut here ] Okt 19 16:00:16 hiltrup kernel: WARNING: CPU: 0 PID: 206 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu] Okt 19 16:00:16 hiltrup kernel: Modules linked in: amdgpu(+) gpu_sched i2c_algo_bit xhci_pci ttm xhci_hcd nvme ahci drm_kms_helper libahci nvme_core usbcore libata r8169 t10_pi crc_t10dif cec realtek crct10dif_generic hid_generic mdio_devres drm crct10dif_pclmul crc32_pclmul crc32c_intel scsi_mod libphy i2c_piix4 usb_common crct10dif_common i2c_hid wmi battery video hid button Okt 19 16:00:16 hiltrup kernel: CPU: 0 PID: 206 Comm: systemd-udevd Not tainted 5.10.0-19-amd64 #1 Debian 5.10.149-1 Okt 19 16:00:16 hiltrup kernel: Hardware name: TUXEDO TUXEDO Pulse 14 Gen1/PULSE1401, BIOS N.1.07.A03 05/11/2021 Okt 19 16:00:16 hiltrup kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu] Okt 19 16:00:16 hiltrup kernel: Code: a8 fd ff ff 01 c7 85 a4 fd ff ff 37 00 00 00 c7 85 ac fd ff ff 20 00 00 00 e8 9d 39 13 00 e9 f4 fa ff ff 0f 0b e9 5f f9 ff ff <0f> 0b e9 af f9 ff ff 0f 0b 0f 0b e9 c6 f9 ff ff 49 8b 06 41 0f b6 Okt 19 16:00:16 hiltrup kernel: RSP: 0018:b2538077b3e0 EFLAGS: 00010002 Okt 19 16:00:16 hiltrup kernel: RAX: 0002 RBX: 0997 RCX: 99ba40b62918 Okt 19 16:00:16 hiltrup kernel: RDX: 0001 RSI: 0297 RDI: 99bac8a20188 Okt 19 16:00:16 hiltrup kernel: RBP: b2538077b6d8 R08: 0005 R09: Okt 19 16:00:16 hiltrup kernel: R10: b2538077b340 R11: b2538077b344 R12: 0297 Okt 19 16:00:16 hiltrup kernel: R13: 99ba40b62800 R14: 99c7f625c000 R15: 99bac8cd1780 Okt 19 16:00:16 hiltrup kernel: FS: 7fea294bb8c0() GS:99c90f60() knlGS: Okt 19 16:00:16 hiltrup kernel: CS: 0010 DS: ES: CR0: 80050033 Okt 19 16:00:16 hiltrup kernel: CR2: 7fea29a4e8cc CR3: 00010bf22000 CR4: 00350ef0 Okt 19 16:00:16 hiltrup kernel: Call Trace: Okt 19 16:00:16 hiltrup kernel: ? __switch_to+0x114/0x460 Okt 19 16:00:16 hiltrup kernel: commit_tail+0x94/0x130 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: drm_client_modeset_commit_atomic+0x1e8/0x230 [drm] Okt 19 16:00:16 hiltrup kernel: drm_client_modeset_commit_locked+0x56/0x160 [drm] Okt 19 16:00:16 hiltrup kernel: drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: fb_pan_display+0x87/0x110 Okt 19 16:00:16 hiltrup kernel: bit_update_start+0x1a/0x40 Okt 19 16:00:16 hiltrup kernel: fbcon_switch+0x31c/0x490 Okt 19 16:00:16 hiltrup kernel: redraw_screen+0xe5/0x250 Okt 19 16:00:16 hiltrup kernel: do_bind_con_driver.isra.0.cold+0xad/0x103 Okt 19 16:00:16 hiltrup kernel: do_take_over_console+0x116/0x190 Okt 19 16:00:16 hiltrup kernel: do_fbcon_takeover+0x5c/0xc0 Okt 19 16:00:16 hiltrup kernel: register_framebuffer+0x1e4/0x300 Okt 19 16:00:16 hiltrup kernel: __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: amdgpu_fbdev_init+0xbd/0x100 [amdgpu] Okt 19 16:00:16 hiltrup kernel: amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu] Okt 19 16:00:16 hiltrup kernel: ? pci_conf1_read+0xa4/0x100 Okt 19 16:00:16 hiltrup kernel: ? pci_bus_read_config_word+0x49/0x70 Okt 19 16:00:16 hiltrup kernel: amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu] Okt 19 16:00:16 hiltrup kernel: amdgpu_pci_probe+0x187/0x210 [amdgpu] Okt 19 16:00:16 hiltrup kernel: local_pci_probe+0x42/0x80 Okt 19 16:00:16 hiltrup kernel: ? _cond_resched+0x16/0x50 Okt 19 16:00:16 hiltrup kernel: pci_device_probe+0x101/0x1b0 Okt 19 16:00:16 hiltrup kernel: really_probe+0x222/0x480 Okt 19 16:00:16
Bug#1022042: marked as done (linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics)
Your message dated Thu, 27 Oct 2022 06:17:10 + with message-id and subject line Bug#1022025: fixed in linux 5.10.149-2 has caused the Debian Bug report #1022025, regarding linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics 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.) -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-amd64 Version: 5.10.149-1 Severity: important X-Debbugs-Cc: autop...@protonmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded to the latest security kernel on Stable (5.10.0-19). After upgrading, I rebooted. * What exactly did you do (or not do) that was effective (or ineffective)? Only thing that works to get 5.10.0-19 booting is to not have integrated AMD graphics. My other nvidia machine upgraded just fine. Disabling modesetting did not resolve the issue. * What was the outcome of this action? Computer gets past GRUB, attempts to boot, and then hangs on a black screen. After about 30 seconds, some error messages are spat out regarding DRM and "flip_done timed out" * What outcome did you expect instead? I expected the machine to boot normally. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-18-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-amd64 depends on: ii linux-image-5.10.0-19-amd64 5.10.149-1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.10.149-2 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 1022...@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: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux Architecture: source Version: 5.10.149-2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1022025 Changes: linux (5.10.149-2) bullseye-security; urgency=high . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 99ea79b0d9c39c38db9c74f1ef43fb92a65842a1 197238 linux_5.10.149-2.dsc 6aae804f7f39a4b87c6bb4568a626c4748798674 3473800 linux_5.10.149-2.debian.tar.xz 4791a4d12ca6778aefe2b8dfd25c3698d38030a4 6718 linux_5.10.149-2_source.buildinfo Checksums-Sha256: 3224be746cd8eb283471d0791ee1132b89bc0485e8c7348b9bce85f15852554e 197238 linux_5.10.149-2.dsc 2efe84aab6aeb700fd0a94f463b4a9f58f45f20e619e54841e962bb2bc03bab3 3473800 linux_5.10.149-2.debian.tar.xz 89916a1b5a0d8bc1ec8fc3be3ea0edccc2b5c5628021d8e2d87643c229b8c31f 6718 linux_5.10.149-2_source.buildinfo Files: e1988377a3b11f75ab8d6e88579d48a0 197238 kernel optional linux_5.10.149-2.dsc c07b55ab29e8a5e6d04233354412a958 3473800 kernel optional linux_5.10.149-2.debian.tar.xz 47eeb1ca50b368e2ed0232e82538460d 6718 kernel optional linux_5.10.149-2_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNTAFhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
Bug#1022025: marked as done (Can't enable amdgpu driver in linux-image-5.10.0-19-amd64)
Your message dated Thu, 27 Oct 2022 06:17:10 + with message-id and subject line Bug#1022025: fixed in linux 5.10.149-2 has caused the Debian Bug report #1022025, regarding Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 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.) -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image Version: 5.10.0-19 Hi, I'm using bulleseye, and upgrate to "linux-image-5.10.0-19" today. Then rebooted, my PC couldn't boot. I pressed a phyisical power button, and force rebooted a PC. I pressed "e" on grub menu, into edit mode for boot options. I edited, GRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.cik_support=0 amdgpu.cik_support=1" to GRUB_CMDLINE_LINUX_DEFAULT="quiet" Then press "F10", a PC could boot. Deleted part "radeon.cik_support=0 amdgpu.cik_support=1" is for enabled "amdgpu" driver instead of "radeon". Of cause, can't enable amdgpu driver after rebooted, and vulkan disabled also. I seems, has problems amdgpu support in a linux-image-5.10.0-19 ? My GPU: $ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.10.149-2 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 1022...@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: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux Architecture: source Version: 5.10.149-2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1022025 Changes: linux (5.10.149-2) bullseye-security; urgency=high . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 99ea79b0d9c39c38db9c74f1ef43fb92a65842a1 197238 linux_5.10.149-2.dsc 6aae804f7f39a4b87c6bb4568a626c4748798674 3473800 linux_5.10.149-2.debian.tar.xz 4791a4d12ca6778aefe2b8dfd25c3698d38030a4 6718 linux_5.10.149-2_source.buildinfo Checksums-Sha256: 3224be746cd8eb283471d0791ee1132b89bc0485e8c7348b9bce85f15852554e 197238 linux_5.10.149-2.dsc 2efe84aab6aeb700fd0a94f463b4a9f58f45f20e619e54841e962bb2bc03bab3 3473800 linux_5.10.149-2.debian.tar.xz 89916a1b5a0d8bc1ec8fc3be3ea0edccc2b5c5628021d8e2d87643c229b8c31f 6718 linux_5.10.149-2_source.buildinfo Files: e1988377a3b11f75ab8d6e88579d48a0 197238 kernel optional linux_5.10.149-2.dsc c07b55ab29e8a5e6d04233354412a958 3473800 kernel optional linux_5.10.149-2.debian.tar.xz 47eeb1ca50b368e2ed0232e82538460d 6718 kernel optional linux_5.10.149-2_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNTAFhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EPTQP/1iEL6iOJpv2OX7wf/l+xXi4s36VgJOU N3fZaRZwDT5oVyWl9A5WVXUR6P2U9t6hJCYI9idRVJ4DRyWTDDzlmOnFAiMCjRDl GoYpnls539pvG8JC7Q8gs5hPFckbARftSZamkxjIc0Y0s6poGG+SPqxTp/cnMBYU xWvURmFtCjjFTLwbl4Vb4GehoAk+ERfQDnSmQrYBauC2hO/0cP0UErypDd+FmuGr GZ2jahvigoRGGLsiJstTf15k/MHijnQSSvvFFCqXh/8Y2A0pdugXTd3feQoMbcFc 3eLXBvbkK4vAoQtIFnY1hqx3iFDs1CqdnBJ6ArEa4orCzYEfZ7/gNHowoAs4lwQa WFwyZDvV+gjMZgmDT87EA6UB7b11qQ8DrMzW81VCdM1y2PrZMCl+zmF4z05OX918 o3WE4AwURQ94W9JAqKsi4QNcHomzIErHtym3oH6Zv2tTVWKWz/XBLO7VNpwxcNJ6 h3FxCTePpI2cIZ04Ht46OZdtrhVWdeRF5/va6lUlL1pENdcRj2D4QfthLgQcBud6 PAozN+hky+ffcT2O/YR/Jz8Nz9tLXaW3fST8mP/Kl4awidGSXutbiqfq3WILIoS2 CnvBDA4I4OETBvpwOex1hWg44sedHofsJL0MKb62ozlOmuEyiKavTDW0UOP5b5vU U+Oz2wg9vkIj =GRlC -END PGP SIGNATURE End Message ---
