It looks like comment #3 had been truncated, the interesting part of the dmesg log that is missing is:
``` [ 66.755306] radeon 0000:01:00.0: ring 0 stalled for more than 31248msec [ 66.755317] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000002 on ring 0) [ 66.840372] radeon 0000:01:00.0: Saved 25 dwords of commands on ring 0. [ 66.840402] radeon 0000:01:00.0: GPU softreset: 0x00000019 [ 66.840408] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA27034A1 [ 66.840414] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000102 [ 66.840419] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200028C0 [ 66.840424] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x04000000 [ 66.840429] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010100 [ 66.840434] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008C80 [ 66.840438] radeon 0000:01:00.0: R_008680_CP_STAT = 0x808182E7 [ 66.840443] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 67.364934] radeon 0000:01:00.0: Wait for MC idle timedout ! [ 67.364940] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007F6B [ 67.365005] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 67.367106] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0x00003028 [ 67.367110] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000002 [ 67.367114] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200028C0 [ 67.367118] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 67.367122] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 67.367126] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 67.367130] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 67.367134] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 67.367152] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 67.842179] radeon 0000:01:00.0: Wait for MC idle timedout ! [ 68.068765] radeon 0000:01:00.0: Wait for MC idle timedout ! [ 68.082273] [drm] PCIE GART of 1024M enabled (table at 0x000000000014C000). [ 68.082448] radeon 0000:01:00.0: WB enabled [ 68.082454] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 [ 68.082459] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c [ 68.088977] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 [ 68.374095] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 68.374176] [drm:rv770_resume [radeon]] *ERROR* r600 startup failed on resume ``` This is what happens when applying the patch to force 32-bit DMA bit mask on PCI devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms Status in linux package in Ubuntu: Confirmed Bug description: This bug is to track specific issues faced by AGP GPUs when running as PCI devices (when AGP support is disabled at kernel build time), unless otherwise proven it is believed fixing #1902795 (PCI GPUs support being broken) may not fix all issues for AGP GPUs running as PCI ones (more to come on that topic). See related bugs: - https://bugs.launchpad.net/bugs/1902795 > PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 - https://bugs.launchpad.net/bugs/1899304 > AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
