Created attachment 142025 [details] journal log when radeon/Xorg crash This is found on Acer Veriton Z4660G desktop equipped with Intel(R) Core(TM) i7-8700 CPU and an AMD/ATI Jet PRO Radeon R5 M230 graphic card. 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230] [1002:6665] (rev 83) Subsystem: PC Partner Limited / Sapphire Technology Jet PRO [Radeon R5 M230] [174b:e332] Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at 90000000 (64-bit, prefetchable) [size=256M] Memory at 7c300000 (64-bit, non-prefetchable) [size=256K] I/O ports at 4000 [size=256] Expansion ROM at 7c340000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [200] #15 Capabilities: [270] #19 Kernel driver in use: radeon Kernel modules: radeon, amdgpu I have tested it with Linux kernel 4.19-rc7. System (radeon module) sometimes hits the error during boot, then Xorg crashes. Oct 12 17:28:52 endless kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 67C0 (len 254, WS 0, PS 4) @ 0x67CE Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 612C (len 78, WS 12, PS 8) @ 0x6165 Oct 12 17:28:52 endless kernel: iwlwifi 0000:00:14.3: HCMD_ACTIVE already clear for command SCAN_REQ_UMAC Oct 12 17:28:52 endless kernel: [drm] PCIE gen 3 link speeds already enabled Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout ! Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout ! Oct 12 17:28:54 endless eos-metrics-ins[606]: Failed to start GeoClue2 client: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying. Oct 12 17:28:54 endless kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: WB enabled Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000007d0c53c5 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x000000006e1c12be Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000a603d5e9 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x0000000039a9e421 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000ba920de2 Oct 12 17:28:55 endless kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) Oct 12 17:28:55 endless kernel: [drm:si_resume [radeon]] *ERROR* si startup failed on resume I also tried to disable radeon's runtime power management by passing "radeon.runpm=0" to boot command. It makes system working stable on this model.
Created attachment 144004 [details] dmesg with Linux kernel 5.1.0-rc5 Tested with Linux kernel 5.1.0-rc5 on this model again. This issue still can be reproduced. cat /sys/module/radeon/parameters/runpm -1 [ 36.906374] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). [ 36.906474] radeon 0000:01:00.0: WB enabled [ 36.906475] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000007764e5ef [ 36.906476] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x00000000acdd696b [ 36.906476] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x0000000094afed91 [ 36.906477] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000b67dc661 [ 36.906477] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000a1f607b2 [ 37.438936] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [ 37.438947] [drm:si_resume [radeon]] *ERROR* si startup failed on resume [ 49.387494] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 49.387514] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 67C0 (len 254, WS 0, PS 4) @ 0x67CE [ 49.387521] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 612C (len 78, WS 12, PS 8) @ 0x6165 [ 49.393021] [drm] PCIE gen 3 link speeds already enabled [ 49.736418] radeon 0000:01:00.0: Wait for MC idle timedout ! [ 49.907902] radeon 0000:01:00.0: Wait for MC idle timedout !
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/857.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.