Bug#1022025: Can't enable amdgpu driver in linux-image-5.10.0-19-amd64

[muumatch]

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]

[Doublychargedhiggs]

Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) hangs on initialisation of amdgpu
driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without any problem.

According to the changelogs on kernel.org there were several changes to amdgpu in versions
5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148.

Some extract from my /var/log/messages just in case it is of any help:

Oct 19 07:05:24 omikron kernel: [ 0.000000] Linux version 5.10.0-19-amd64 (debian...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 (2022-10-17)
Oct 19 07:05:24 omikron kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off snd_hda_intel.power_save=0
...
Oct 19 07:05:24 omikron kernel: [ 2.325914] [drm] amdgpu kernel modesetting enabled.
Oct 19 07:05:24 omikron kernel: [ 2.327288] amdgpu: Topology: Add APU node [0x0:0x0]
Oct 19 07:05:24 omikron kernel: [ 2.327398] fb0: switching to amdgpudrmfb from EFI VGA
Oct 19 07:05:24 omikron kernel: [ 2.328120] Console: switching to colour dummy device 80x25
Oct 19 07:05:24 omikron kernel: [ 2.328366] amdgpu 0000:05:00.0: vgaarb: deactivate vga console
Oct 19 07:05:24 omikron kernel: [ 2.328431] amdgpu 0000:05:00.0: enabling device (0006 -> 0007)
Oct 19 07:05:24 omikron kernel: [ 2.328516] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83).
Oct 19 07:05:24 omikron kernel: [ 2.328519] amdgpu 0000:05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
Oct 19 07:05:24 omikron kernel: [ 2.328536] [drm] register mmio base: 0xFE600000
Oct 19 07:05:24 omikron kernel: [ 2.328537] [drm] register mmio size: 524288
Oct 19 07:05:24 omikron kernel: [ 2.328559] [drm] add ip block number 0 <soc15_common>
Oct 19 07:05:24 omikron kernel: [ 2.328561] [drm] add ip block number 1 <gmc_v9_0>
Oct 19 07:05:24 omikron kernel: [ 2.328562] [drm] add ip block number 2 <vega10_ih>
Oct 19 07:05:24 omikron kernel: [ 2.328564] [drm] add ip block number 3 <psp>
Oct 19 07:05:24 omikron kernel: [ 2.328565] [drm] add ip block number 4 <gfx_v9_0>
Oct 19 07:05:24 omikron kernel: [ 2.328567] [drm] add ip block number 5 <sdma_v4_0>
Oct 19 07:05:24 omikron kernel: [ 2.328568] [drm] add ip block number 6 <powerplay>
Oct 19 07:05:24 omikron kernel: [ 2.328570] [drm] add ip block number 7 <dm>
Oct 19 07:05:24 omikron kernel: [ 2.328571] [drm] add ip block number 8 <vcn_v1_0>
Oct 19 07:05:24 omikron kernel: [ 2.333054] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input6
Oct 19 07:05:24 omikron kernel: [ 2.334135] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_gpu_info.bin
Oct 19 07:05:24 omikron kernel: [ 2.334155] amdgpu 0000:05:00.0: amdgpu: Fetched VBIOS from VFCT
Oct 19 07:05:24 omikron kernel: [ 2.334157] amdgpu: ATOM BIOS: 113-RAVEN-113
Oct 19 07:05:24 omikron kernel: [ 2.334462] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_sdma.bin
Oct 19 07:05:24 omikron kernel: [ 2.334469] [drm] VCN decode is enabled in VM mode
Oct 19 07:05:24 omikron kernel: [ 2.334470] [drm] VCN encode is enabled in VM mode
Oct 19 07:05:24 omikron kernel: [ 2.334471] [drm] JPEG decode is enabled in VM mode
Oct 19 07:05:24 omikron kernel: [ 2.334527] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Oct 19 07:05:24 omikron kernel: [ 2.334539] amdgpu 0000:05:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
Oct 19 07:05:24 omikron kernel: [ 2.334541] amdgpu 0000:05:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
Oct 19 07:05:24 omikron kernel: [ 2.334543] amdgpu 0000:05:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Oct 19 07:05:24 omikron kernel: [ 2.334551] [drm] Detected VRAM RAM=2048M, BAR=2048M
Oct 19 07:05:24 omikron kernel: [ 2.334552] [drm] RAM width 128bits DDR4
Oct 19 07:05:24 omikron kernel: [ 2.334618] [TTM] Zone kernel: Available graphics memory: 15381802 KiB
Oct 19 07:05:24 omikron kernel: [ 2.334620] [TTM] Zone dma32: Available graphics memory: 2097152 KiB
Oct 19 07:05:24 omikron kernel: [ 2.334621] [TTM] Initializing pool allocator
Oct 19 07:05:24 omikron kernel: [ 2.334626] [TTM] Initializing DMA pool allocator
Oct 19 07:05:24 omikron kernel: [ 2.334738] [drm] amdgpu: 2048M of VRAM memory ready
Oct 19 07:05:24 omikron kernel: [ 2.334741] [drm] amdgpu: 3072M of GTT memory ready.
Oct 19 07:05:24 omikron kernel: [ 2.334744] [drm] GART: num cpu pages 262144, num gpu pages 262144
Oct 19 07:05:24 omikron kernel: [ 2.335166] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
Oct 19 07:05:24 omikron kernel: [ 2.336034] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_asd.bin
Oct 19 07:05:24 omikron kernel: [ 2.336227] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_ta.bin
Oct 19 07:05:24 omikron kernel: [ 2.336520] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_pfp.bin
Oct 19 07:05:24 omikron kernel: [ 2.336623] kvm: Nested Virtualization enabled
Oct 19 07:05:24 omikron kernel: [ 2.336642] SVM: kvm: Nested Paging enabled
Oct 19 07:05:24 omikron kernel: [ 2.336643] SVM: Virtual VMLOAD VMSAVE supported
Oct 19 07:05:24 omikron kernel: [ 2.336644] SVM: Virtual GIF supported
Oct 19 07:05:24 omikron kernel: [ 2.336691] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_me.bin
Oct 19 07:05:24 omikron kernel: [ 2.336916] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_ce.bin
Oct 19 07:05:24 omikron kernel: [ 2.337206] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_rlc.bin
Oct 19 07:05:24 omikron kernel: [ 2.338242] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 3168, REV=0x220
Oct 19 07:05:24 omikron kernel: [ 2.339481] MCE: In-kernel MCE decoding enabled.
Oct 19 07:05:24 omikron kernel: [ 2.339625] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_mec.bin
Oct 19 07:05:24 omikron kernel: [ 2.341904] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_mec2.bin
Oct 19 07:05:24 omikron kernel: [ 2.342607] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.342695] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.344202] amdgpu: hwmgr_sw_init smu backed is smu10_smu
Oct 19 07:05:24 omikron kernel: [ 2.345059] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_vcn.bin
Oct 19 07:05:24 omikron kernel: [ 2.345070] [drm] Found VCN firmware Version ENC: 1.12 DEC: 2 VEP: 0 Revision: 1
Oct 19 07:05:24 omikron kernel: [ 2.345082] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
Oct 19 07:05:24 omikron kernel: [ 2.357223] iwlwifi 0000:03:00.0: base HW address: b4:6b:fc:aa:39:3f
Oct 19 07:05:24 omikron kernel: [ 2.366322] [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
...
Oct 19 07:05:24 omikron kernel: [ 2.439861] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.439951] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.536277] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.536372] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.592055] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.592139] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.599182] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
Oct 19 07:05:24 omikron kernel: [ 2.627223] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
Oct 19 07:05:24 omikron kernel: [ 2.629224] [drm] kiq ring mec 2 pipe 1 q 0
Oct 19 07:05:24 omikron kernel: [ 2.630115] [drm] DM_PPLIB: values for F clock
Oct 19 07:05:24 omikron kernel: [ 2.630117] [drm] DM_PPLIB: 400000 in kHz, 3174 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630118] [drm] DM_PPLIB: 933000 in kHz, 3724 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630119] [drm] DM_PPLIB: 1067000 in kHz, 3924 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630120] [drm] DM_PPLIB: 1200000 in kHz, 4074 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630122] [drm] DM_PPLIB: values for DCF clock
Oct 19 07:05:24 omikron kernel: [ 2.630123] [drm] DM_PPLIB: 300000 in kHz, 3174 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630124] [drm] DM_PPLIB: 600000 in kHz, 3724 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630125] [drm] DM_PPLIB: 626000 in kHz, 3924 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630126] [drm] DM_PPLIB: 654000 in kHz, 4074 in mV
Oct 19 07:05:24 omikron kernel: [ 2.630456] [drm] Display Core initialized with v3.2.104!
Oct 19 07:05:24 omikron kernel: [ 2.642269] snd_hda_intel 0000:05:00.1: bound 0000:05:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Oct 19 07:05:24 omikron kernel: [ 2.676121] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.676234] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.679131] [drm] VCN decode and encode initialized successfully(under SPG Mode).
Oct 19 07:05:24 omikron kernel: [ 2.680984] kfd kfd: Allocated 3969056 bytes on gart
Oct 19 07:05:24 omikron kernel: [ 2.682017] amdgpu 0000:05:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 11, active_cu_number 8
Oct 19 07:05:24 omikron kernel: [ 2.744334] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.744389] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.796114] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.796177] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 2.864259] EDAC amd64: F17h_M10h detected (node 0).
Oct 19 07:05:24 omikron kernel: [ 2.864323] EDAC amd64: Node 0: DRAM ECC disabled.
Oct 19 07:05:24 omikron kernel: [ 3.207209] [drm] Fence fallback timer expired on ring sdma0
Oct 19 07:05:24 omikron kernel: [ 3.207232] [drm] fb mappable at 0x60BCA000
Oct 19 07:05:24 omikron kernel: [ 3.207234] [drm] vram apper at 0x60000000
Oct 19 07:05:24 omikron kernel: [ 3.207235] [drm] size 8294400
Oct 19 07:05:24 omikron kernel: [ 3.207237] [drm] fb depth is 24
Oct 19 07:05:24 omikron kernel: [ 3.207238] [drm] pitch is 7680
Oct 19 07:05:24 omikron kernel: [ 3.207392] fbcon: amdgpudrmfb (fb0) is primary device
Oct 19 07:05:24 omikron kernel: [ 3.286888] Console: switching to colour frame buffer device 240x67
Oct 19 07:05:24 omikron kernel: [ 33.831265] ------------[ cut here ]------------
Oct 19 07:05:24 omikron kernel: [ 33.831454] WARNING: CPU: 2 PID: 468 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.831455] Modules linked in: joydev snd_hda_codec_realtek edac_mce_amd snd_hda_codec_generic iwlmvm kvm_amd ledtrig_audio snd_hda_codec_hdmi hid_generic snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation kvm mac80211 amdgpu(+) snd_soc_core irqbypass cdc_acm ghash_clmulni_intel snd_compress soundwire_cadence snd_hda_codec gpu_sched ttm snd_hda_core libarc4 drm_kms_helper snd_hwdep soundwire_bus aesni_intel snd_pcm_oss cec snd_mixer_oss libaes usbhid iwlwifi snd_pcm crypto_simd drm cryptd glue_helper snd_timer sp5100_tco cfg80211 rapl efi_pstore pcspkr k10temp watchdog snd i2c_algo_bit ccp snd_rn_pci_acp3x snd_pci_acp3x soundcore rfkill rng_core cm32181 evdev industrialio button acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic mmc_block ahci libahci xhci_pci xhci_hcd libata nvme r8169 crc32_pclmul crc32c_intel usbcore realtek scsi_mod mdio_devres nvme_core libphy i2c_piix4 i2c_amd_mp2_pci sdhci_acpi t10_pi usb_common crc_t10dif sdhci crct10dif_generic
Oct 19 07:05:24 omikron kernel: [ 33.831525] crct10dif_pclmul crct10dif_common mmc_core video i2c_hid hid
Oct 19 07:05:24 omikron kernel: [ 33.831533] CPU: 2 PID: 468 Comm: systemd-udevd Not tainted 5.10.0-19-amd64 #1 Debian 5.10.149-1
Oct 19 07:05:24 omikron kernel: [ 33.831534] Hardware name: Seco C40/C40, BIOS 1.08 04/23/2020
Oct 19 07:05:24 omikron kernel: [ 33.831705] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.831709] 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 07:05:24 omikron kernel: [ 33.831711] RSP: 0018:ffffc270002ef3e0 EFLAGS: 00010002
Oct 19 07:05:24 omikron kernel: [ 33.831713] RAX: 0000000000000002 RBX: 000000000000072b RCX: ffff9df3c7dae118
Oct 19 07:05:24 omikron kernel: [ 33.831715] RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff9df3c2d80188
Oct 19 07:05:24 omikron kernel: [ 33.831716] RBP: ffffc270002ef6d8 R08: 0000000000000005 R09: 0000000000000000
Oct 19 07:05:24 omikron kernel: [ 33.831717] R10: ffffc270002ef340 R11: ffffc270002ef344 R12: 0000000000000297
Oct 19 07:05:24 omikron kernel: [ 33.831718] R13: ffff9df3c7dae000 R14: ffff9df3c0e5fe00 R15: ffff9df3e141de80
Oct 19 07:05:24 omikron kernel: [ 33.831720] FS: 00007f89d412d8c0(0000) GS:ffff9dfac0e80000(0000) knlGS:0000000000000000
Oct 19 07:05:24 omikron kernel: [ 33.831721] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 19 07:05:24 omikron kernel: [ 33.831723] CR2: 00007fe922eefb50 CR3: 0000000104042000 CR4: 00000000003506e0
Oct 19 07:05:24 omikron kernel: [ 33.831724] Call Trace:
Oct 19 07:05:24 omikron kernel: [ 33.831738] ? __switch_to+0x114/0x460
Oct 19 07:05:24 omikron kernel: [ 33.831755] commit_tail+0x94/0x130 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.831769] drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.831795] drm_client_modeset_commit_atomic+0x1e8/0x230 [drm]
Oct 19 07:05:24 omikron kernel: [ 33.831818] drm_client_modeset_commit_locked+0x56/0x160 [drm]
Oct 19 07:05:24 omikron kernel: [ 33.831830] drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.831838] fb_pan_display+0x87/0x110
Oct 19 07:05:24 omikron kernel: [ 33.831841] bit_update_start+0x1a/0x40
Oct 19 07:05:24 omikron kernel: [ 33.831844] fbcon_switch+0x31c/0x490
Oct 19 07:05:24 omikron kernel: [ 33.831851] redraw_screen+0xe5/0x250
Oct 19 07:05:24 omikron kernel: [ 33.831856] do_bind_con_driver.isra.0.cold+0xad/0x103
Oct 19 07:05:24 omikron kernel: [ 33.831859] do_take_over_console+0x116/0x190
Oct 19 07:05:24 omikron kernel: [ 33.831862] do_fbcon_takeover+0x5c/0xc0
Oct 19 07:05:24 omikron kernel: [ 33.831864] register_framebuffer+0x1e4/0x300
Oct 19 07:05:24 omikron kernel: [ 33.831877] __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.832001] amdgpu_fbdev_init+0xbd/0x100 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832173] amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832181] ? pci_conf1_read+0xa4/0x100
Oct 19 07:05:24 omikron kernel: [ 33.832187] ? pwm_get+0xfe/0x2a0
Oct 19 07:05:24 omikron kernel: [ 33.832314] amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832432] amdgpu_pci_probe+0x187/0x210 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832438] local_pci_probe+0x42/0x80
Oct 19 07:05:24 omikron kernel: [ 33.832442] ? _cond_resched+0x16/0x50
Oct 19 07:05:24 omikron kernel: [ 33.832445] pci_device_probe+0x101/0x1b
0
Oct 19 07:05:24 omikron kernel: [ 33.832449] really_probe+0x222/0x480
Oct 19 07:05:24 omikron kernel: [ 33.832453] driver_probe_device+0xe5/0x150
Oct 19 07:05:24 omikron kernel: [ 33.832456] device_driver_attach+0xa9/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.832459] __driver_attach+0xb5/0x170
Oct 19 07:05:24 omikron kernel: [ 33.832461] ? device_driver_attach+0xb0/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.832463] ? device_driver_attach+0xb0/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.832465] bus_for_each_dev+0x78/0xc0
Oct 19 07:05:24 omikron kernel: [ 33.832469] bus_add_driver+0x13a/0x200
Oct 19 07:05:24 omikron kernel: [ 33.832472] driver_register+0x8b/0xe0
Oct 19 07:05:24 omikron kernel: [ 33.832474] ? 0xffffffffc1e8b000
Oct 19 07:05:24 omikron kernel: [ 33.832477] do_one_initcall+0x44/0x1d0
Oct 19 07:05:24 omikron kernel: [ 33.832481] ? do_init_module+0x23/0x250
Oct 19 07:05:24 omikron kernel: [ 33.832485] ? kmem_cache_alloc_trace+0xf5/0x200
Oct 19 07:05:24 omikron kernel: [ 33.832488] do_init_module+0x4c/0x250
Oct 19 07:05:24 omikron kernel: [ 33.832491] __do_sys_finit_module+0xb1/0x120
Oct 19 07:05:24 omikron kernel: [ 33.832495] do_syscall_64+0x33/0x80
Oct 19 07:05:24 omikron kernel: [ 33.832498] entry_SYSCALL_64_after_hwframe+0x61/0xc6
Oct 19 07:05:24 omikron kernel: [ 33.832500] RIP: 0033:0x7f89d45e43a9
Oct 19 07:05:24 omikron kernel: [ 33.832503] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 8a 0d 00 f7 d8 64 89 01 48
Oct 19 07:05:24 omikron kernel: [ 33.832504] RSP: 002b:00007fff26e75908 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Oct 19 07:05:24 omikron kernel: [ 33.832506] RAX: ffffffffffffffda RBX: 000055df9c0e69d0 RCX: 00007f89d45e43a9
Oct 19 07:05:24 omikron kernel: [ 33.832507] RDX: 0000000000000000 RSI: 00007f89d4781e2d RDI: 0000000000000012
Oct 19 07:05:24 omikron kernel: [ 33.832508] RBP: 0000000000020000 R08: 0000000000000000 R09: 000055df9a1c960e
Oct 19 07:05:24 omikron kernel: [ 33.832509] R10: 0000000000000012 R11: 0000000000000246 R12: 00007f89d4781e2d
Oct 19 07:05:24 omikron kernel: [ 33.832510] R13: 0000000000000000 R14: 000055df9c0fcc30 R15: 000055df9c0e69d0
Oct 19 07:05:24 omikron kernel: [ 33.832513] ---[ end trace 0fcfc56e406b09fe ]---
Oct 19 07:05:24 omikron kernel: [ 33.832529] ------------[ cut here ]------------
Oct 19 07:05:24 omikron kernel: [ 33.832697] WARNING: CPU: 2 PID: 468 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6992 amdgpu_dm_atomic_commit_tail+0x23b8/0x2440 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832698] Modules linked in: joydev snd_hda_codec_realtek edac_mce_amd snd_hda_codec_generic iwlmvm kvm_amd ledtrig_audio snd_hda_codec_hdmi hid_generic snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation kvm mac80211 amdgpu(+) snd_soc_core irqbypass cdc_acm ghash_clmulni_intel snd_compress soundwire_cadence snd_hda_codec gpu_sched ttm snd_hda_core libarc4 drm_kms_helper snd_hwdep soundwire_bus aesni_intel snd_pcm_oss cec snd_mixer_oss libaes usbhid iwlwifi snd_pcm crypto_simd drm cryptd glue_helper snd_timer sp5100_tco cfg80211 rapl efi_pstore pcspkr k10temp watchdog snd i2c_algo_bit ccp snd_rn_pci_acp3x snd_pci_acp3x soundcore rfkill rng_core cm32181 evdev industrialio button acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic mmc_block ahci libahci xhci_pci xhci_hcd libata nvme r8169 crc32_pclmul crc32c_intel usbcore realtek scsi_mod mdio_devres nvme_core libphy i2c_piix4 i2c_amd_mp2_pci sdhci_acpi t10_pi usb_common crc_t10dif sdhci crct10dif_generic
Oct 19 07:05:24 omikron kernel: [ 33.832737] crct10dif_pclmul crct10dif_common mmc_core video i2c_hid hid
Oct 19 07:05:24 omikron kernel: [ 33.832741] CPU: 2 PID: 468 Comm: systemd-udevd Tainted: G W 5.10.0-19-amd64 #1 Debian 5.10.149-1
Oct 19 07:05:24 omikron kernel: [ 33.832742] Hardware name: Seco C40/C40, BIOS 1.08 04/23/2020
Oct 19 07:05:24 omikron kernel: [ 33.832908] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x23b8/0x2440 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.832910] Code: 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 8e 2d 01 00 00 48 c7 c6 58
Oct 19 07:05:24 omikron kernel: [ 33.832911] RSP: 0018:ffffc270002ef3e0 EFLAGS: 00010082
Oct 19 07:05:24 omikron kernel: [ 33.832913] RAX: 0000000000000001 RBX: 000000000000072b RCX: ffff9df3c7dae118
Oct 19 07:05:24 omikron kernel: [ 33.832914] RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff9df3c2d80188
Oct 19 07:05:24 omikron kernel: [ 33.832915] RBP: ffffc270002ef6d8 R08: 0000000000000005 R09: 0000000000000000
Oct 19 07:05:24 omikron kernel: [ 33.832916] R10: ffffc270002ef340 R11: ffffc270002ef344 R12: 0000000000000297
Oct 19 07:05:24 omikron kernel: [ 33.832917] R13: ffff9df3c7dae000 R14: ffff9df3c0e5fe00 R15: ffff9df3e141de80
Oct 19 07:05:24 omikron kernel: [ 33.832918] FS: 00007f89d412d8c0(0000) GS:ffff9dfac0e80000(0000) knlGS:0000000000000000
Oct 19 07:05:24 omikron kernel: [ 33.832920] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 19 07:05:24 omikron kernel: [ 33.832920] CR2: 00007fe922eefb50 CR3: 0000000104042000 CR4: 00000000003506e0
Oct 19 07:05:24 omikron kernel: [ 33.832921] Call Trace:
Oct 19 07:05:24 omikron kernel: [ 33.832928] ? __switch_to+0x114/0x460
Oct 19 07:05:24 omikron kernel: [ 33.832944] commit_tail+0x94/0x130 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.832957] drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.832978] drm_client_modeset_commit_atomic+0x1e8/0x230 [drm]
Oct 19 07:05:24 omikron kernel: [ 33.833000] drm_client_modeset_commit_locked+0x56/0x160 [drm]
Oct 19 07:05:24 omikron kernel: [ 33.833011] drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.833015] fb_pan_display+0x87/0x110
Oct 19 07:05:24 omikron kernel: [ 33.833017] bit_update_start+0x1a/0x40
Oct 19 07:05:24 omikron kernel: [ 33.833019] fbcon_switch+0x31c/0x490
Oct 19 07:05:24 omikron kernel: [ 33.833023] redraw_screen+0xe5/0x250
Oct 19 07:05:24 omikron kernel: [ 33.833026] do_bind_con_driver.isra.0.cold+0xad/0x103
Oct 19 07:05:24 omikron kernel: [ 33.833029] do_take_over_console+0x116/0x190
Oct 19 07:05:24 omikron kernel: [ 33.833031] do_fbcon_takeover+0x5c/0xc0
Oct 19 07:05:24 omikron kernel: [ 33.833034] register_framebuffer+0x1e4/0x300
Oct 19 07:05:24 omikron kernel: [ 33.833045] __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper]
Oct 19 07:05:24 omikron kernel: [ 33.833169] amdgpu_fbdev_init+0xbd/0x100 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.833337] amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.833340] ? pci_conf1_read+0xa4/0x100
Oct 19 07:05:24 omikron kernel: [ 33.833343] ? pwm_get+0xfe/0x2a0
Oct 19 07:05:24 omikron kernel: [ 33.833461] amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.833580] amdgpu_pci_probe+0x187/0x210 [amdgpu]
Oct 19 07:05:24 omikron kernel: [ 33.833583] local_pci_probe+0x42/0x80
Oct 19 07:05:24 omikron kernel: [ 33.833585] ? _cond_resched+0x16/0x50
Oct 19 07:05:24 omikron kernel: [ 33.833588] pci_device_probe+0x101/0x1b
0
Oct 19 07:05:24 omikron kernel: [ 33.833591] really_probe+0x222/0x480
Oct 19 07:05:24 omikron kernel: [ 33.833594] driver_probe_device+0xe5/0x150
Oct 19 07:05:24 omikron kernel: [ 33.833596] device_driver_attach+0xa9/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.833599] __driver_attach+0xb5/0x170
Oct 19 07:05:24 omikron kernel: [ 33.833601] ? device_driver_attach+0xb0/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.833603] ? device_driver_attach+0xb0/0xb0
Oct 19 07:05:24 omikron kernel: [ 33.833605] bus_for_each_dev+0x78/0xc0
Oct 19 07:05:24 omikron kernel: [ 33.833608] bus_add_driver+0x13a/0x200
Oct 19 07:05:24 omikron kernel: [ 33.833610] driver_register+0x8b/0xe0
Oct 19 07:05:24 omikron kernel: [ 33.833612] ? 0xffffffffc1e8b000
Oct 19 07:05:24 omikron kernel: [ 33.833614] do_one_initcall+0x44/0x1d0
Oct 19 07:05:24 omikron kernel: [ 33.833617] ? do_init_module+0x23/0x250
Oct 19 07:05:24 omikron kernel: [ 33.833619] ? kmem_cache_alloc_trace+0xf5/0x200
Oct 19 07:05:24 omikron kernel: [ 33.833622] do_init_module+0x4c/0x250
Oct 19 07:05:24 omikron kernel: [ 33.833624] __do_sys_finit_module+0xb1/0x120
Oct 19 07:05:24 omikron kernel: [ 33.833628] do_syscall_64+0x33/0x80
Oct 19 07:05:24 omikron kernel: [ 33.833630] entry_SYSCALL_64_after_hwframe+0x61/0xc6
Oct 19 07:05:24 omikron kernel: [ 33.833632] RIP: 0033:0x7f89d45e43a9
Oct 19 07:05:24 omikron kernel: [ 33.833634] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 8a 0d 00 f7 d8 64 89 01 48
Oct 19 07:05:24 omikron kernel: [ 33.833635] RSP: 002b:00007fff26e75908 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Oct 19 07:05:24 omikron kernel: [ 33.833637] RAX: ffffffffffffffda RBX: 000055df9c0e69d0 RCX: 00007f89d45e43a9
Oct 19 07:05:24 omikron kernel: [ 33.833638] RDX: 0000000000000000 RSI: 00007f89d4781e2d RDI: 0000000000000012
Oct 19 07:05:24 omikron kernel: [ 33.833639] RBP: 0000000000020000 R08: 0000000000000000 R09: 000055df9a1c960e
Oct 19 07:05:24 omikron kernel: [ 33.833639] R10: 0000000000000012 R11: 0000000000000246 R12: 00007f89d4781e2d
Oct 19 07:05:24 omikron kernel: [ 33.833640] R13: 0000000000000000 R14: 000055df9c0fcc30 R15: 000055df9c0e69d0
Oct 19 07:05:24 omikron kernel: [ 33.833643] ---[ end trace 0fcfc56e406b09ff ]---
Oct 19 07:05:24 omikron kernel: [ 44.078485] amdgpu 0000:05:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Oct 19 07:05:24 omikron kernel: [ 44.091577] amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091580] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091582] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091584] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091585] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091587] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091589] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091591] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091593] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091595] amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Oct 19 07:05:24 omikron kernel: [ 44.091597] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Oct 19 07:05:24 omikron kernel: [ 44.091599] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Oct 19 07:05:24 omikron kernel: [ 44.091601] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Oct 19 07:05:24 omikron kernel: [ 44.091602] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Oct 19 07:05:24 omikron kernel: [ 44.091604] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Oct 19 07:05:24 omikron kernel: [ 44.096790] [drm] Initialized amdgpu 3.40.0 20150101 for 0000:05:00.0 on minor 0
Oct 19 07:05:24 omikron kernel: [ 46.631181] [drm] Fence fallback timer expired on ring gfx
Oct 19 07:05:24 omikron kernel: [ 47.143176] [drm] Fence fallback timer expired on ring comp_1.0.0
Oct 19 07:05:24 omikron kernel: [ 47.655186] [drm] Fence fallback timer expired on ring comp_1.1.0
Oct 19 07:05:24 omikron kernel: [ 48.167176] [drm] Fence fallback timer expired on ring comp_1.2.0
Oct 19 07:05:24 omikron kernel: [ 48.679177] [drm] Fence fallback timer expired on ring comp_1.3.0
Oct 19 07:05:24 omikron kernel: [ 49.191185] [drm] Fence fallback timer expired on ring comp_1.0.1
Oct 19 07:05:24 omikron kernel: [ 49.703187] [drm] Fence fallback timer expired on ring comp_1.1.1
Oct 19 07:05:24 omikron kernel: [ 50.215178] [drm] Fence fallback timer expired on ring comp_1.2.1
Oct 19 07:05:24 omikron kernel: [ 50.727176] [drm] Fence fallback timer expired on ring comp_1.3.1
Oct 19 07:05:24 omikron kernel: [ 51.239176] [drm] Fence fallback timer expired on ring sdma0
Oct 19 07:05:24 omikron kernel: [ 51.783203] [drm] Fence fallback timer expired on ring vcn_dec
Oct 19 07:05:24 omikron kernel: [ 52.295176] [drm] Fence fallback timer expired on ring vcn_enc0
Oct 19 07:05:24 omikron kernel: [ 52.807174] [drm] Fence fallback timer expired on ring vcn_enc1
Oct 19 07:05:24 omikron kernel: [ 53.319184] [drm] Fence fallback timer expired on ring jpeg_dec
Oct 19 07:05:24 omikron kernel: [ 64.551267] ------------[ cut here ]------------
Oct 19 07:05:24 omikron kernel: [ 64.551449] WARNING: CPU: 2 PID: 103 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu]

... and so on forever ...

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi,

There are two commits queued for the next 5.10.y upload which revert
changes affecting drm/admgpu. It would be great if you can confirm
applying the attached two patches resolve the issue.

Regards,
Salvatore

[Dan Coleman]

Hi,

I would love to, but I'm afraid I don't know how. If you or anyone on the chain is willing to show me what commands to enter (I tried following this https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html but got as far as 4.2.2 and couldn't find a debian directory in the source that I unpacked by following the prior instructions), I would be grateful.

That said, I understand time and resources are limited, so no worries if that's not possible!

Best,

Dan

>> Oct 19 07:05:24 omikron kernel: [ 33.831755] commit_tail+0x94/0x130 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.831769] drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.831795] drm_client_modeset_commit_atomic+0x1e8/0x230 [drm]
>> Oct 19 07:05:24 omikron kernel: [ 33.831818] drm_client_modeset_commit_locked+0x56/0x160 [drm]
>> Oct 19 07:05:24 omikron kernel: [ 33.831830] drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.831838] fb_pan_display+0x87/0x11

0

>> Oct 19 07:05:24 omikron kernel: [ 33.831841] bit_update_start+0x1a/0x40
>> Oct 19 07:05:24 omikron kernel: [ 33.831844] fbcon_switch+0x31c/0x490
>> Oct 19 07:05:24 omikron kernel: [ 33.831851] redraw_screen+0xe5/0x250
>> Oct 19 07:05:24 omikron kernel: [ 33.831856] do_bind_con_driver.isra.0.cold+0xad/0x103
>> Oct 19 07:05:24 omikron kernel: [ 33.831859] do_take_over_console+0x116/0x190
>> Oct 19 07:05:24 omikron kernel: [ 33.831862] do_fbcon_takeover+0x5c/0xc0
>> Oct 19 07:05:24 omikron kernel: [ 33.831864] register_framebuffer+0x1e4/0x300
>> Oct 19 07:05:24 omikron kernel: [ 33.831877] __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.832001] amdgpu_fbdev_init+0xbd/0x100 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.832173] amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.832181] ? pci_conf1_read+0xa4/0x100
>> Oct 19 07:05:24 omikron kernel: [ 33.832187] ? pwm_get+0xfe/0x2a0
>> Oct 19 07:05:24 omikron kernel: [ 33.832314] amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.832432] amdgpu_pci_probe+0x187/0x210 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.832438] local_pci_probe+0x42/0x8

0
>> Oct 19 07:05:24 omikron kernel: [ 33.832442] ? _cond_resched+0x16/0x5
0

>> Oct 19 07:05:24 omikron kernel: [ 33.832445] pci_device_probe+0x101/0x1b0
>> Oct 19 07:05:24 omikron kernel: [ 33.832449] really_probe+0x222/0x480
>> Oct 19 07:05:24 omikron kernel: [ 33.832453] driver_probe_device+0xe5/0x150
>> Oct 19 07:05:24 omikron kernel: [ 33.832456] device_driver_attach+0xa9/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.832459] __driver_attach+0xb5/0x170
>> Oct 19 07:05:24 omikron kernel: [ 33.832461] ? device_driver_attach+0xb0/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.832463] ? device_driver_attach+0xb0/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.832465] bus_for_each_dev+0x78/0xc0
>> Oct 19 07:05:24 omikron kernel: [ 33.832469] bus_add_driver+0x13a/0x200
>> Oct 19 07:05:24 omikron kernel: [ 33.832472] driver_register+0x8b/0xe

0

>> Oct 19 07:05:24 omikron kernel: [ 33.832474] ? 0xffffffffc1e8b000
>> Oct 19 07:05:24 omikron kernel: [ 33.832477] do_one_initcall+0x44/0x1d0
>> Oct 19 07:05:24 omikron kernel: [ 33.832481] ? do_init_module+0x23/0x250
>> Oct 19 07:05:24 omikron kernel: [ 33.832485] ? kmem_cache_alloc_trace+0xf5/0x200
>> Oct 19 07:05:24 omikron kernel: [ 33.832488] do_init_module+0x4c/0x25

0

0

>> Oct 19 07:05:24 omikron kernel: [ 33.832944] commit_tail+0x94/0x130 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.832957] drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.832978] drm_client_modeset_commit_atomic+0x1e8/0x230 [drm]
>> Oct 19 07:05:24 omikron kernel: [ 33.833000] drm_client_modeset_commit_locked+0x56/0x160 [drm]
>> Oct 19 07:05:24 omikron kernel: [ 33.833011] drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.833015] fb_pan_display+0x87/0x11

0

>> Oct 19 07:05:24 omikron kernel: [ 33.833017] bit_update_start+0x1a/0x40
>> Oct 19 07:05:24 omikron kernel: [ 33.833019] fbcon_switch+0x31c/0x490
>> Oct 19 07:05:24 omikron kernel: [ 33.833023] redraw_screen+0xe5/0x250
>> Oct 19 07:05:24 omikron kernel: [ 33.833026] do_bind_con_driver.isra.0.cold+0xad/0x103
>> Oct 19 07:05:24 omikron kernel: [ 33.833029] do_take_over_console+0x116/0x190
>> Oct 19 07:05:24 omikron kernel: [ 33.833031] do_fbcon_takeover+0x5c/0xc0
>> Oct 19 07:05:24 omikron kernel: [ 33.833034] register_framebuffer+0x1e4/0x300
>> Oct 19 07:05:24 omikron kernel: [ 33.833045] __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper]
>> Oct 19 07:05:24 omikron kernel: [ 33.833169] amdgpu_fbdev_init+0xbd/0x100 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.833337] amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.833340] ? pci_conf1_read+0xa4/0x100
>> Oct 19 07:05:24 omikron kernel: [ 33.833343] ? pwm_get+0xfe/0x2a0
>> Oct 19 07:05:24 omikron kernel: [ 33.833461] amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.833580] amdgpu_pci_probe+0x187/0x210 [amdgpu]
>> Oct 19 07:05:24 omikron kernel: [ 33.833583] local_pci_probe+0x42/0x8

0
>> Oct 19 07:05:24 omikron kernel: [ 33.833585] ? _cond_resched+0x16/0x5
0

>> Oct 19 07:05:24 omikron kernel: [ 33.833588] pci_device_probe+0x101/0x1b0
>> Oct 19 07:05:24 omikron kernel: [ 33.833591] really_probe+0x222/0x480
>> Oct 19 07:05:24 omikron kernel: [ 33.833594] driver_probe_device+0xe5/0x150
>> Oct 19 07:05:24 omikron kernel: [ 33.833596] device_driver_attach+0xa9/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.833599] __driver_attach+0xb5/0x170
>> Oct 19 07:05:24 omikron kernel: [ 33.833601] ? device_driver_attach+0xb0/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.833603] ? device_driver_attach+0xb0/0xb0
>> Oct 19 07:05:24 omikron kernel: [ 33.833605] bus_for_each_dev+0x78/0xc0
>> Oct 19 07:05:24 omikron kernel: [ 33.833608] bus_add_driver+0x13a/0x200
>> Oct 19 07:05:24 omikron kernel: [ 33.833610] driver_register+0x8b/0xe

0

>> Oct 19 07:05:24 omikron kernel: [ 33.833612] ? 0xffffffffc1e8b000
>> Oct 19 07:05:24 omikron kernel: [ 33.833614] do_one_initcall+0x44/0x1d0
>> Oct 19 07:05:24 omikron kernel: [ 33.833617] ? do_init_module+0x23/0x250
>> Oct 19 07:05:24 omikron kernel: [ 33.833619] ? kmem_cache_alloc_trace+0xf5/0x200
>> Oct 19 07:05:24 omikron kernel: [ 33.833622] do_init_module+0x4c/0x25

0

[Salvatore Bonaccorso]

Hi Dan,

On Wed, Oct 19, 2022 at 12:55:16PM +0000, Dan Coleman wrote:
> Hi,
>
> I would love to, but I'm afraid I don't know how. If you or anyone on the chain is willing to show me what commands to enter (I tried following this https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html but got as far as 4.2.2 and couldn't find a debian directory in the source that I unpacked by following the prior instructions), I would be grateful.
>
> That said, I understand time and resources are limited, so no worries if that's not possible!

When you do fetch the source package the output will look like:

# apt-get source linux
Reading package lists... Done
NOTICE: 'linux' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/kernel-team/linux.git
Please use:
git clone https://salsa.debian.org/kernel-team/linux.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 124 MB of source archives.
Get:1 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (dsc) [197 kB]
Get:2 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (tar) [122 MB]
Get:3 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (diff) [1549 kB]
Fetched 124 MB in 1s (95.7 MB/s)
dpkg-source: info: extracting linux in linux-5.10.149
dpkg-source: info: unpacking linux_5.10.149.orig.tar.xz
dpkg-source: info: unpacking linux_5.10.149-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying debian/gitignore.patch
dpkg-source: info: applying debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch
[...]
dpkg-source: info: applying bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch
dpkg-source: info: applying bugfix/all/bpftool-fix-version-string-in-recursive-builds.patch
dpkg-source: info: applying debian/overlayfs-permit-mounts-in-userns.patch

Now you have in the current working directory the linux-5.10.149 directory.

Did you process went that far? If so change into that directory where the debian/
directory which will include the debian/bin/test-patches to test-apply the patches
we would like to test.

If that will not help I will try to respin a build so anyone affected can test

Hope this helps already,

Regards,
Salvatore

[Dan Coleman]

Hi,

I've built the test kernel successfully, how do I install it? I have the following four files.

linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb

linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb

linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb

linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb

On 10/19/22 08:18 AM, Salvatore Bonaccorso wrote:
> Hi Dan,
>
> On Wed, Oct 19, 2022 at 12:55:16PM +0000, Dan Coleman wrote:
>> Hi,
>>

>> I would love to, but I'm afraid I don't know how. If you or anyone on the chain is willing to show me what commands to enter (I tried following thishttps://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html but got as far as 4.2.2 and couldn't find a debian directory in the source that I unpacked by following the prior instructions), I would be grateful.

>>
>> That said, I understand time and resources are limited, so no worries if that's not possible!
> When you do fetch the source package the output will look like:
>
> # apt-get source linux
> Reading package lists... Done
> NOTICE: 'linux' packaging is maintained in the 'Git' version control system at:
> https://salsa.debian.org/kernel-team/linux.git
> Please use:

> git clonehttps://salsa.debian.org/kernel-team/linux.git

> to retrieve the latest (possibly unreleased) updates to the package.
> Need to get 124 MB of source archives.

> Get:1http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (dsc) [197 kB]
> Get:2http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (tar) [122 MB]
> Get:3http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (diff) [1549 kB]

[Dan Coleman]

$ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ...
dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help):
 linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1)
  linux-image-5.10.0-19-amd64 is to be removed.

dpkg: regarding .../linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb containing linux-image-5.10.0-19-amd64-unsigned:
 linux-image-5.10.0-19-amd64-unsigned conflicts with linux-image-5.10.0-19-amd64
  linux-image-5.10.0-19-amd64 (version 5.10.149-1) is present and installed.

dpkg: error processing archive ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb (--install):
 conflicting packages - not installing linux-image-5.10.0-19-amd64-unsigned
Errors were encountered while processing:
 ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb

On 10/19/22 09:32 AM, Diederik de Haas wrote:

> On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote:
>> I've built the test kernel successfully, how do I install it? I have the
>> following four files.
>>
>> linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb
>> linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb
>> linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
>> linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb

> # = do as root or with 'sudo'
>
> # dpkg -i linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb

[Diederik de Haas]

On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote:

> I've built the test kernel successfully, how do I install it? I have the
> following four files.
>
> linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb
> linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb
> linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
> linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb

[Diederik de Haas]

On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote:
> $ sudo dpkg -i
> ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg:
> considering removing linux-image-5.10.0-19-amd64 in favour of
> linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with
> removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help):
> linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1)
> linux-image-5.10.0-19-amd64 is to be removed.

AFAICT, the last line indicates the problem.
I do know how I would resolve it on my system and if my initial attempt fails
how to fix that, but I don't feel comfortable suggesting that to you.

So, I'll let Salvatore take over as he's (WAY) more experienced then I am.

[Salvatore Bonaccorso]

Hi Dan, hi Diederik

You need to have (temporarily at least) removed the signed package
indeed, as they are conflicting. If you do it with apt-get install
./path/to/local/package.deb all the surronding work should be done as
well.

(And you have the 18 ABI kernel still installed to which you can go
back if th test package does no work).

After testing, make sure to reinstall the linux-image-amd64 package
again.

Regards,
Salvatore

[Dan Coleman]

Ok, I think I succeeded in getting the test kernel to install, but it did not solve the issue. The fans ramped up a bit, and I didn't get any errors about DRM on the console, but it still hung on the black screen.

Of course, I may have royally screwed up installing the kernel (thank goodness for Timeshift), so I welcome another, more experienced tester to verify my own findings.

[Dan Coleman]

I'm recompiling to start from scratch and make sure I did this correctly, but I'll be away from my computer for several hours. If anyone else wants to jump in and report their own findings, feel free! Hopefully there's some new info when I get back.

Thanks very much to Salvatore and Diederik for their help.

On 10/19/22 10:38 AM, Dan Coleman wrote:
> Ok, I think I succeeded in getting the test kernel to install, but it did not solve the issue. The fans ramped up a bit, and I didn't get any errors about DRM on the console, but it still hung on the black screen.
>
> Of course, I may have royally screwed up installing the kernel (thank goodness for Timeshift), so I welcome another, more experienced tester to verify my own findings.
>
> On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote:

[Marcus Orthbandt]

I have checked something.

All three System have completly same installation:

On Athlon 220GE without seperate graphics card)
After Update to 5.10.0-19 first Blank Screen, after a lot of Time (~30 Minutes) comes Lightdm up, but each Keystroke need Minutes!
So i think wie CPU are very very slowly.

On Ryzen 3 3250U without seperate graphics card)
Same effect, but i have not testet to wait until Ligthdm comes up.

On Ryzen 5 2400G with separate Graphics AMD Radeon RX570)
No Failure

I hope it helps to detect the issue.

Marcus

Am 19.10.22 um 15:31 schrieb Salvatore Bonaccorso:

Hi Marcus,

On Wed, Oct 19, 2022 at 02:57:40PM +0200, PC-vor-Ort, Marcus Orthbandt wrote:

Hello Kernel-Team,

the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on
AMD-Machines.

do you know these Bug currently?

Can you have a look if the following matches your issue:
https://bugs.debian.org/1022025

Regards,
Salvatore

[Dan Coleman]

I tried again, same result. Either the patches aren't working OR I don't adequately know how to install test kernels. In no uncertain terms, it could very well be my lack of knowledge and ability in this regard.

[Felix Miata]

Original problem confirmed here. Booting prior kernel works fine:
# xdriinfo
Screen 0: radeonsi
# pinxi -C --vs
pinxi 3.3.22-08 (2022-10-18)
CPU:
Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
bits: 64 type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 1700 min/max: 1700/3700 cores: 1: 1700 2: 1700 3: 1700
4: 1700
# pinxi -GSaz
System:
Kernel: 5.10.0-14-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz.old root=LABEL=<filter> noresume
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
radeon.cik_support=0 amdgpu.cik_support=1 video=1440x900@60 5
Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 ports:
active: DP-1,DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0
chip-ID: 1002:130f class-ID: 0300
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l
model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60
dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD KAVERI (DRM 3.40.0
5.10.0-14-amd64 LLVM 11.0.1) direct render: Yes

Booting is not prevented with radeon.cik_support=1 amdgpu.cik_support=0 instead of
radeon.cik_support=0 amdgpu.cik_support=1 on Grub linu line, but X doesn't start.
https://paste.debian.net/plain/1257669 and https://paste.debian.net/plain/1257670
are Xorg.0.logs from booting with none of those boot parameters, the latter from
attempting to force use of the modesetting DIX display driver via
/etc/X11/xorg.conf.d/.

https://paste.debian.net/plain/1257668 is last 100 lines of journal from attempt
to boot normally with 5.10.0-19 and radeon.cik_support=0 amdgpu.cik_support=1.
--
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

[Dan Coleman]

Looks like there's some attention upstream.

https://bugzilla.kernel.org/show_bug.cgi?id=216608

https://gitlab.freedesktop.org/drm/amd/-/issues/2216

[Diederik de Haas]

Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Control: tag -1 +patch

On Thursday, 20 October 2022 14:44:34 CEST Dan Coleman wrote:
> Looks like there's some attention upstream.
>

> https://gitlab.freedesktop.org/drm/amd/-/issues/2216

That looks like a proper analyses, thanks!
It also includes a patch which I included here for convenience.

It would be really useful if you/someone could build a kernel with that patch
to see whether it fixes the issue.

[Salvatore Bonaccorso]

# raising severity for now
Control: severity -1 serious

Hi,

On Wed, Oct 19, 2022 at 10:01:58PM +0000, Dan Coleman wrote:
> I tried again, same result. Either the patches aren't working OR I
> don't adequately know how to install test kernels. In no uncertain
> terms, it could very well be my lack of knowledge and ability in
> this regard.

On the https://gitlab.freedesktop.org/drm/amd/-/issues/2216 Alex
Deucher is claiming the issue should be fixed by
https://gitlab.freedesktop.org/drm/amd/-/issues/2216#note_1599805 .

So can you (or someone else affected) try next the attached patch?

(interestingly though the mentioned commit which uncovers the issue
was first applied in 5.10.137, then reverted in 5.10.141, so it's
unclear why the issue would still manifest).

Else if anyone with affected hardware is able to bisect between
5.10.140 and 5.10.149 that would be great.

Regards,
Salvatore

[Diederik de Haas]

On Thursday, 20 October 2022 16:34:47 CEST Diederik de Haas wrote:
> On Thursday, 20 October 2022 14:44:34 CEST Dan Coleman wrote:
> > Looks like there's some attention upstream.
> >
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2216
>
> That looks like a proper analyses, thanks!
> It also includes a patch which I included here for convenience.

The patch is also available via 'lore' here:
https://lore.kernel.org/all/20221020034809.50652...@amd.com/

[Doublychargedhiggs]

Did the same as Dan, i.e built the kernel (apt-get install source) with the upstream proposed patch
0001-drm-amdgpu-fix-sdma-doorbell-init-ordering-on-APUs.patch
using the mentioned test-patches script. The kernel really builds, is even installable, but then hangs
as before at boot, as Dan reported before.

However, i'm even less experienced kernel builder than Dan (my 1st kernel build ever)...

[Diederik de Haas]

On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote:
> > Apparently "test-patches" does not build a 'headers-common' package and
> > therefor installing the headers failed which in turn made DKMS fail.
>
> That seems like less-than-ideal behavior for test-patches.
> Is that a bug that would benefit from being reported?

I don't know because:

> > but for testing this particular issue/patch it is sufficient.

But OTOH, it does build a deb file for the 'normal' linux-headers and that
seems useless without the linux-headers-common deb file.
I'm inclined to think: either build both or build neither.

[Diederik de Haas]

On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:
> So there are two patches who need to be reverted:
>
> https://lore.kernel.org/stable/20221020153857.56516...@amd.com/
> https://lore.kernel.org/stable/20221020153857.56516...@amd.com/

https://lore.kernel.org/stable/2651645.mvXUDI8C0e@bagend/ is where I indicated
that applying those 2 patches (IOW reverting 2 commits) fixes the issue for me.

https://mateloos.be/~diederik/kernel/fix-stable-amdgpu-issue-bug-1022025/
is where I uploaded the *.deb files I build. (They'll be removed shortly again)

HTH,
Diederik

[Doublychargedhiggs]

Confirmed, the two patches work for me too (AMD Ryzen Embedded V1605B with Radeon Vega Gfx).
Kernel rebuilt and now boots like a charm and works without further issues.
Thanks to all of you!!

[Christoph Zechner]

On Thu, 20 Oct 2022 18:36:21 +0200 Diederik de Haas
<didi....@cknow.org> wrote:
> On Thursday, 20 October 2022 17:36:33 CEST Christoph Zechner wrote:
> > I hope this helps, if there's something additional I could contribute,
> > please let me know!
>
> It's probably best to participate in the upstream issue here:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Thank you for the pointer, I submitted my information there as well.


On Thu, 20 Oct 2022 22:10:27 +0200 Salvatore Bonaccorso
<car...@debian.org> wrote:> Hi all,

> So there are two patches who need to be reverted:
>
>
https://lore.kernel.org/stable/20221020153857.56516...@amd.com/
>
https://lore.kernel.org/stable/20221020153857.56516...@amd.com/
>

> Salvatore

Perfect, thank you, this solved the issue on my machine (Ryzen 7 PRO
4750U) as well.

Best regards
Christoph Zechner

[Salvatore Bonaccorso]

Hi,

On Fri, Oct 21, 2022 at 12:55:09PM +0000, Dan Coleman wrote:
> Hey,

>
> > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:
>

> > > So there are two patches who need to be reverted:
> > >
> > > https://lore.kernel.org/stable/20221020153857.56516...@amd.com/
> > > https://lore.kernel.org/stable/20221020153857.56516...@amd.com/
>
>

> How do I apply these patches to see if they work for me? Thus far in
> this bug, I've just seen .patch files.

Here are those as patches.

If you trust unsigned binary packages build I would put somehwere I
can provide you those with those two applied. But again, after testing
make sure you reinstall the meta package and go back to the -18
version.

Regards,
Salvatore

[Michael Becker]

5.10.149-2 solved the problem
many thanks for the quick fix



-------- Weitergeleitete Nachricht --------
Betreff: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
Datum: Wed, 19 Oct 2022 14:33:04 +0000
Von: Debian Bug Tracking System <ow...@bugs.debian.org>
Antwort an: 102...@bugs.debian.org
An: Michael <mjbe...@web.de>

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
Debian Kernel Team <debian...@lists.debian.org>

If you wish to submit further information on this problem, please
send it to 102...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

--
1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Dan Coleman]

Revised kernel works for me as well! Thanks everyone for the rapid response.

[inasprecali]

On Thu, 27 Oct 2022 06:17:10 +0000 Debian FTP Masters
<ftpm...@ftp-master.debian.org> wrote:
> Source: linux
> Source-Version: 5.10.149-2
> Done: Salvatore Bonaccorso <car...@debian.org>
>
> 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

[Felix Miata]

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.

[Jorge Barreiro]

Just wanted to report that version 5.10.149-2 fixed the issue for me. Using
"AMD Ryzen 5 PRO 4650G with Radeon Graphics" with its integraded graphics.

[muumatch]

> 5.10.149-2 was no help with A10-7850K Radeon R7.

Yes, My PC didn't boot with amdgpu yet, on linux-image-5.10.0-19-amd64.
I'm using Radeon R7 Graphics too.
I'm a man that 1st post in this thread.
Sorry, I was so busy for a while.

Attached /var/log/messages when didn't boot.