Bug 95247 - System hangs after ~10 minutes when using Radeon R9 390
Summary: System hangs after ~10 minutes when using Radeon R9 390
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-03 06:46 UTC by Sandeep
Modified: 2019-11-19 09:16 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Full dmesg log 4.6-rc6 (1.11 MB, text/plain)
2016-05-12 05:40 UTC, Sandeep
no flags Details
Dmesg log - Linux 4.6 (72.92 KB, text/plain)
2016-06-04 19:38 UTC, Sandeep
no flags Details
Dmesg log - Linux 4.6.1 (119.49 KB, text/plain)
2016-06-06 03:36 UTC, Sandeep
no flags Details

Description Sandeep 2016-05-03 06:46:28 UTC
Hardware specs:
Intel Core i5-6600k
MSI Z170A Gaming Pro motherboard
Radeon R9 390

Boot system with Radeon R9 390 as main output (by choosing PEG as output in UEFI settings).
Started up Gnome Wayland session. System hangs after some time. Does not respond to keyboard and mouse input. Cannot switch to TTYs either. Can however restart the system using Ctrl + Alt + PrtScr R-S-E-I-S-U-B

Works perfectly fine with the integrated Intel GPU.
Comment 1 Sandeep 2016-05-03 06:51:55 UTC
Found the following in kernel logs:
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10052msec
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000121ff last fence id 0x0000000000012209 on ring 0)
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: ring 4 stalled for more than 10084msec
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000b547 last fence id 0x000000000000b548 on ring 4)
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: ring 3 stalled for more than 10128msec
May 02 23:37:31 GetsugaTenshou kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002c7c last fence id 0x0000000000002c7d on ring 3)
Comment 2 Sandeep 2016-05-03 06:53:52 UTC
May 02 23:37:32 GetsugaTenshou kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
May 02 23:37:32 GetsugaTenshou kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
May 02 23:37:32 GetsugaTenshou kernel: [drm] probing gen 2 caps for device 8086:1901 = 261ad03/e
May 02 23:37:32 GetsugaTenshou kernel: [drm] PCIE gen 3 link speeds already enabled
May 02 23:37:32 GetsugaTenshou kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000324000).
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: WB enabled
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000200000c00 and cpu addr 0xffff880459248c00
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000200000c04 and cpu addr 0xffff880459248c04
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000200000c08 and cpu addr 0xffff880459248c08
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000200000c0c and cpu addr 0xffff880459248c0c
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000200000c10 and cpu addr 0xffff880459248c10
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000076c98 and cpu addr 0xffffc90004c36c98
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000200000c18 and cpu addr 0xffff880459248c18
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000200000c1c and cpu addr 0xffff880459248c1c
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 0 succeeded in 4 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 1 succeeded in 3 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 2 succeeded in 2 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 3 succeeded in 5 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 4 succeeded in 5 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 5 succeeded in 2 usecs
May 02 23:37:32 GetsugaTenshou kernel: sysrq: SysRq : Emergency Sync
May 02 23:37:32 GetsugaTenshou kernel: [drm] UVD initialized successfully.
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 6 succeeded in 1168 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 7 succeeded in 4 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] VCE initialized successfully.
May 02 23:37:32 GetsugaTenshou kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
May 02 23:37:32 GetsugaTenshou kernel: [drm] ib test on ring 0 succeeded in 0 usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Comment 3 Oded Gabbay 2016-05-04 07:31:21 UTC
Could you please attach dmesg and "lspci -nn" ?
Comment 4 Sandeep 2016-05-12 05:40:42 UTC
Created attachment 123638 [details]
Full dmesg log 4.6-rc6
Comment 5 Sandeep 2016-06-04 19:38:20 UTC
Created attachment 124318 [details]
Dmesg log - Linux 4.6
Comment 6 Sandeep 2016-06-06 03:36:09 UTC
Created attachment 124347 [details]
Dmesg log - Linux 4.6.1

GPU reset occurred while replaying Metro 2033 Redux OpenGL calls using apitrace replay functionality.
Comment 7 Sandeep 2016-08-06 20:35:34 UTC
00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)
00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911]
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)
00:1d.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #11 [8086:a11a] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] [1002:67b1] (rev 80)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [1002:aac8]
03:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
05:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03)
Comment 8 Sandeep 2016-10-10 04:39:39 UTC
I am using the AMDGPU driver for my card, and it works quite well. Much more stable, no hangs now and performance also seems better.
Comment 9 Martin Peres 2019-11-19 09:16:00 UTC
-- 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/713.


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.