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
