Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that. I tried booting 5.10.0-19 with an empty command line string and it worked, although it’s now using the "radeon" gpu driver while I’d like to use the "amdgpu" driver instead, mainly for better Vulkan support. Booting with command line options to disable "radeon" and enable "amdgpu" works for 5.10.0-18 and earlier. I don’t know if this an entirely separate issue, however. I can file a separate bug if you think it is appropriate. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On Sunday, 23 October 2022 15:15:36 CEST inasprecali wrote: > It does not boot at all, I'm unable to SSH into it. It's not > merely that the display does not work. Then I'm inclined to think this *is* a separate issue, which is due to the upgrade to -19, but that you happen to have an AMD GPU is 'not' relevant. On Sunday, 23 October 2022 15:18:03 CEST inasprecali wrote: > In my case, it's because, without command line parameters, the > kernel will select the "radeon" driver, while I want to use the > "amdgpu" driver instead. > > The options "radeon.si_support=0 amdgpu.si_support=1" disable > radeon support and enable amdgpu support respectively. I realize it's not what you want, but may result in an useful extra data point if you (for this test) switch those parameters to enable radeon support and disable amdgpu support. Can you try that? If that test does not make a difference, then I'm quite sure it's a separate issue and it would be best to open a new bug report for that. signature.asc Description: This is a digitally signed message part.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On Sun, 23 Oct 2022 13:40:26 +0200 Diederik de Haas wrote: > Does it really not boot? Or does the screen not work properly? > > The cases in this bug report all boot AFAIK, it's just that the screen does > not work properly, but people were able to SSH into the machine. > If your system actually does not boot, then I'm inclined to think that that is > a different problem. It does not boot at all, I'm unable to SSH into it. It's not merely that the display does not work. At the moment, I'm unable to provide additional information, but I'll try looking into it as soon as possible. Best regards -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On zondag 23 oktober 2022 12:02:52 CEST inasprecali wrote: > After updating to the latest version (5.10.149-2), my system > running an AMD GPU and CPU still does not boot. I am unable to > retrieve any logs from the systemd journal. Does it really not boot? Or does the screen not work properly? The cases in this bug report all boot AFAIK, it's just that the screen does not work properly, but people were able to SSH into the machine. If your system actually does not boot, then I'm inclined to think that that is a different problem. signature.asc Description: This is a digitally signed message part.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
After updating to the latest version (5.10.149-2), my system running an AMD GPU and CPU still does not boot. I am unable to retrieve any logs from the systemd journal. CPU: AMD FX-8350 GPU: AMD R9 270X (Southern Islands Family) Kernel command line parameters: GRUB_CMDLINE_LINUX="radeon.si_support=0 amdgpu.si_support=1" 5.10.0-19 fails to boot, while 5.10.0-18 does. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Dear maintainer, I can confirm this bug too. Processor is an AMD Ryzen 5 5600G with Radeon Graphics. It doesn't boot (at least not in ~10min) and displays only the mentioned "flip_done timed out" messages. 5.10.0-18-amd64 works normally. Best regards, Andreas
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Can confirm this issue with a AMD Ryzen 3 2200G Processor with Vega 8 Graphics on a AsRock DeskMini A300.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
I can confirm this same exact problem on a machine of mine. CPU: AMD FX-8350 GPU: AMD R9 270X (Southern Islands Family) 5.10.0-19 fails to boot, while 5.10.0-18 does. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Failed to boot kernel 5.10.0-19 with: CPU: AMD Ryzen 7 3800X (16) (no integrated graphics) GPU: AMD ATI Radeon Vega Frontier Edition No issues with kernel 5.10.0-18. --- Ian
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
I can confirm too AMD® Ryzen 7 4700u with radeon graphics × 8 AMD® Renoir
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Same thing here with an AMD Ryzen 5 PRO 3400G system. Also gnome-shell have been complaining about "Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 62 failed: Permission denied" for some time. I don't know what is CRTC 62, but clearly it is related.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Dear Maintainer, i can confirm the problem. All of our notebooks with integrated AMD graphics (CPU: AMD Ryzen 7 PRO 4750U with Radeon Graphics) are affected and don't boot anymore. During boot the following error-messages appear: [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. 5.10.0-18 boots without problems. Best Regards, Arndt Kaiser
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
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
