Hello, On Mon, Mar 24, 2025 at 07:12:28PM -0300, Matías Teplitzky wrote: > *** Reporter, please consider answering these questions, where appropriate *** > > I'm reporting this bug from the machine having this problem. As the subject > states, all of a sudden, I'm getting a blank screen at the end of the boot > process, > with no video output at all!. I've no GUI and video output remains > unresponsive when trying to change and use any TTY. However, I was able to > connect through SSH, > enabling it by blindly typing login creds and propper commands. Thus, I was > able to gather some information. > > >From kernel messages extracted with "sudo journalctl -b -g amdgpu": > > ----- > > Mar 24 12:19:14 debian-desktop kernel: [drm] amdgpu kernel modesetting > enabled. > Mar 24 12:19:14 debian-desktop kernel: amdgpu: Virtual CRAT table created for > CPU > Mar 24 12:19:14 debian-desktop kernel: amdgpu: Topology: Add CPU node > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: enabling device > (0006 -> 0007) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: Fetched > VBIOS from VFCT > Mar 24 12:19:14 debian-desktop kernel: amdgpu: ATOM BIOS: 113-RAVEN2-117 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: vgaarb: > deactivate vga console > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: Trusted > Memory Zone (TMZ) feature enabled > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: VRAM: > 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: GART: > 1024M 0x0000000000000000 - 0x000000003FFFFFFF > Mar 24 12:19:14 debian-desktop kernel: [drm] amdgpu: 2048M of VRAM memory > ready > Mar 24 12:19:14 debian-desktop kernel: [drm] amdgpu: 6960M of GTT memory > ready. > Mar 24 12:19:14 debian-desktop kernel: amdgpu: hwmgr_sw_init smu backed is > smu10_smu > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: reserve > 0x400000 from 0xf47fc00000 for PSP TMR > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: failed to > load ucode RLC_RESTORE_LIST_CNTL(0x29) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx > command LOAD_IP_FW(0x6) failed and response status is (0xFFFF300F) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: failed to > load ucode RLC_RESTORE_LIST_GPM_MEM(0x2A) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx > command LOAD_IP_FW(0x6) failed and response status is (0xFFFF000F) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: failed to > load ucode RLC_RESTORE_LIST_SRM_MEM(0x2B) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx > command LOAD_IP_FW(0x6) failed and response status is (0xFFFF000F) > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: RAS: > optional ras ta ucode is not available > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: RAP: > optional rap ta ucode is not available > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: > SECUREDISPLAY: securedisplay ta ucode is not available > Mar 24 12:19:14 debian-desktop kernel: snd_hda_intel 0000:04:00.1: bound > 0000:04:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) > Mar 24 12:19:14 debian-desktop kernel: kfd kfd: amdgpu: Allocated 3969056 > bytes on gart > Mar 24 12:19:14 debian-desktop kernel: kfd kfd: amdgpu: Total number of KFD > nodes to be created: 1 > Mar 24 12:19:14 debian-desktop kernel: amdgpu: Virtual CRAT table created for > GPU > Mar 24 12:19:14 debian-desktop kernel: amdgpu: Topology: Add dGPU node > [0x15d8:0x1002] > Mar 24 12:19:14 debian-desktop kernel: kfd kfd: amdgpu: added device 1002:15d8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: SE 1, SH > per SE 1, CU per SH 3, active_cu_number 3 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx > uses VM inv eng 0 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.0.0 uses VM inv eng 1 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.1.0 uses VM inv eng 4 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.2.0 uses VM inv eng 5 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.3.0 uses VM inv eng 6 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.0.1 uses VM inv eng 7 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.1.1 uses VM inv eng 8 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.2.1 uses VM inv eng 9 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > comp_1.3.1 uses VM inv eng 10 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > kiq_0.2.1.0 uses VM inv eng 11 on hub 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > sdma0 uses VM inv eng 0 on hub 8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > vcn_dec uses VM inv eng 1 on hub 8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > vcn_enc0 uses VM inv eng 4 on hub 8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > vcn_enc1 uses VM inv eng 5 on hub 8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: ring > jpeg_dec uses VM inv eng 6 on hub 8 > Mar 24 12:19:14 debian-desktop kernel: amdgpu: pp_dpm_get_sclk_od was not > implemented. > Mar 24 12:19:14 debian-desktop kernel: amdgpu: pp_dpm_get_mclk_od was not > implemented. > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: amdgpu: Runtime > PM not available > Mar 24 12:19:14 debian-desktop kernel: [drm] Initialized amdgpu 3.61.0 for > 0000:04:00.0 on minor 0 > Mar 24 12:19:14 debian-desktop kernel: amdgpu 0000:04:00.0: [drm] Cannot find > any crtc or sizes > > ----- > > In particular, this line caught my attention: "amdgpu 0000:04:00.0: [drm] > Cannot find any crtc or sizes". Soon, > I found that booting with "nomodeset" as a kernel argument, I was able to get > video output but unable to load a GUI > (I'm using wayland with sway). I understand that this is due to disabling KMS > kernel driver. > > After doing some digging on the Internet, I found that booting with > "amd_iommu=off" should work and it did!. Note that > information gathered below, is the result from booting with that kernel > paramater as a workaorund. > > > * What led up to the situation? > > I don't know, really!. If I recall correctly, I've been using the > "linux-image-6.12.17-amd64" kernel for maybe a week > and this problem didn't occur. Once faced with this problem, I tried doing an > "apt upgrade" and tried with the updated > kernel version "linux-image-6.12.19-amd64", but it didn't work. This problem > persisted with several reboots and a power off and > on again cycle. I also tried booting with older kernel versions, but didn't > help either.
I wonder if you did a *real* cold boot between your tests. Sometimes not all components are properly reset on a warm restart. So ideally unplug power for a moment between tests. I guess the grub boot menu is shown before Linux is started? Can you provide a full boot log for a boot without amd_iommu=off? Best regards Uwe
signature.asc
Description: PGP signature
