dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196197] New: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Date: Tue, 27 Jun 2017 08:53:51 +0000	[thread overview]
Message-ID: <bug-196197-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 196197
           Summary: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0
                    test failed (scratch(0x8504)=0xCAFEDEAD)
           Product: Drivers
           Version: 2.5
    Kernel Version: linux-image-4.11.7-towo.1-siduction-amd64
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: anbro@ok.de
        Regression: No

Created attachment 257191
  --> https://bugzilla.kernel.org/attachment.cgi?id=257191&action=edit
Bug report as a text file with line feed

Dear maintainer,

Every time the system is booting it will hang, when trying to start Xorg every
5 seconds in an endless loop. The keyboard is locked too.
Only possibility to get a console is via ssh from another machine.

The bug is reproducible always and can always be avoided by downgrading to a
kernel 4.10, leaving the rest of the system unchanged.
That bug comes with the step from kernel 4.10 to kernel 4.11.

Hardware:
AMD Opteron Board with graphics card in a PCI-E 8x Slot.
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV630
XT [Radeon HD 2600 XT]

Relevant sections of kern.log:
Jun  4 09:19:41 a1 kernel: [   46.719247] radeon 0000:06:00.0: ring 0 stalled
for more than 10093msec
Jun  4 09:19:41 a1 kernel: [   46.719253] radeon 0000:06:00.0: GPU lockup
(current fence id 0x000000000000000e last fence id 0x0000000000000
012 on ring 0)
Jun  4 09:19:41 a1 kernel: [   46.729651] radeon 0000:06:00.0: Saved 121 dwords
of commands on ring 0.
Jun  4 09:19:41 a1 kernel: [   46.729666] radeon 0000:06:00.0: GPU softreset:
0x00000019
Jun  4 09:19:41 a1 kernel: [   46.729669] radeon 0000:06:00.0:  
R_008010_GRBM_STATUS      = 0xE57C24E0
Jun  4 09:19:41 a1 kernel: [   46.729672] radeon 0000:06:00.0:  
R_008014_GRBM_STATUS2     = 0x00113303
Jun  4 09:19:41 a1 kernel: [   46.729674] radeon 0000:06:00.0:  
R_000E50_SRBM_STATUS      = 0x200030C0
Jun  4 09:19:41 a1 kernel: [   46.729676] radeon 0000:06:00.0:  
R_008674_CP_STALLED_STAT1 = 0x01000000
Jun  4 09:19:41 a1 kernel: [   46.729678] radeon 0000:06:00.0:  
R_008678_CP_STALLED_STAT2 = 0x00001002
Jun  4 09:19:41 a1 kernel: [   46.729680] radeon 0000:06:00.0:  
R_00867C_CP_BUSY_STAT     = 0x00028C86
Jun  4 09:19:41 a1 kernel: [   46.729683] radeon 0000:06:00.0:  
R_008680_CP_STAT          = 0x808386C5
Jun  4 09:19:41 a1 kernel: [   46.729685] radeon 0000:06:00.0:  
R_00D034_DMA_STATUS_REG   = 0x44C83D57
Jun  4 09:19:41 a1 kernel: [   46.965016] radeon 0000:06:00.0:
R_008020_GRBM_SOFT_RESET=0x00007FEF
Jun  4 09:19:41 a1 kernel: [   46.965070] radeon 0000:06:00.0:
SRBM_SOFT_RESET=0x00000100
Jun  4 09:19:41 a1 kernel: [   46.967176] radeon 0000:06:00.0:  
R_008010_GRBM_STATUS      = 0xA0003030
Jun  4 09:19:41 a1 kernel: [   46.967178] radeon 0000:06:00.0:  
R_008014_GRBM_STATUS2     = 0x00000003
Jun  4 09:19:41 a1 kernel: [   46.967181] radeon 0000:06:00.0:  
R_000E50_SRBM_STATUS      = 0x2000B0C0
Jun  4 09:19:41 a1 kernel: [   46.967183] radeon 0000:06:00.0:  
R_008674_CP_STALLED_STAT1 = 0x00000000
Jun  4 09:19:41 a1 kernel: [   46.967185] radeon 0000:06:00.0:  
R_008678_CP_STALLED_STAT2 = 0x00000000
Jun  4 09:19:41 a1 kernel: [   46.967187] radeon 0000:06:00.0:  
R_00867C_CP_BUSY_STAT     = 0x00000000
Jun  4 09:19:41 a1 kernel: [   46.967189] radeon 0000:06:00.0:  
R_008680_CP_STAT          = 0x80100000
Jun  4 09:19:41 a1 kernel: [   46.967191] radeon 0000:06:00.0:  
R_00D034_DMA_STATUS_REG   = 0x44C83D57
Jun  4 09:19:41 a1 kernel: [   46.967200] radeon 0000:06:00.0: GPU reset
succeeded, trying to resume
Jun  4 09:19:41 a1 kernel: [   47.139539] [drm] PCIE GART of 512M enabled
(table at 0x0000000000142000).
Jun  4 09:19:41 a1 kernel: [   47.139556] radeon 0000:06:00.0: WB enabled
Jun  4 09:19:41 a1 kernel: [   47.139559] radeon 0000:06:00.0: fence driver on
ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff880
33fc2cc00
Jun  4 09:19:41 a1 kernel: [   47.140372] radeon 0000:06:00.0: fence driver on
ring 5 use gpu addr 0x00000000000521d0 and cpu addr 0xffffc90
004a121d0
Jun  4 09:19:42 a1 kernel: [   47.343830] [drm:r600_ring_test [radeon]] *ERROR*
radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Jun  4 09:19:42 a1 kernel: [   47.343855] [drm:r600_resume [radeon]] *ERROR*
r600 startup failed on resume
Jun  4 09:19:52 a1 kernel: [   57.358140] radeon 0000:06:00.0: ring 0 stalled
for more than 10186msec
Jun  4 09:19:52 a1 kernel: [   57.358148] radeon 0000:06:00.0: GPU lockup
(current fence id 0x000000000000000e last fence id 0x0000000000000
012 on ring 0)
Jun  4 09:19:52 a1 kernel: [   57.367850] radeon 0000:06:00.0: Saved 261817
dwords of commands on ring 0.
Jun  4 09:19:52 a1 kernel: [   57.367866] radeon 0000:06:00.0: GPU softreset:
0x00000008
Jun  4 09:19:52 a1 kernel: [   57.367869] radeon 0000:06:00.0:  
R_008010_GRBM_STATUS      = 0xA0003030
Jun  4 09:19:52 a1 kernel: [   57.367871] radeon 0000:06:00.0:  
R_008014_GRBM_STATUS2     = 0x00000003



Greetings,
Andreas

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-06-27  8:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  8:53 bugzilla-daemon [this message]
2017-06-27  8:59 ` [Bug 196197] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) bugzilla-daemon
2017-06-27 17:24 ` bugzilla-daemon
2017-06-29  2:44 ` bugzilla-daemon
2017-06-29  9:26 ` bugzilla-daemon
2017-06-29  9:45 ` bugzilla-daemon
2017-06-30  7:41 ` bugzilla-daemon
2017-06-30 14:09 ` bugzilla-daemon
2017-07-13 17:42 ` bugzilla-daemon
2017-07-17 15:16 ` bugzilla-daemon
2017-07-21 12:38 ` bugzilla-daemon
2017-11-02 19:34 ` bugzilla-daemon
2017-11-03  9:12 ` bugzilla-daemon
2017-12-19 16:51 ` bugzilla-daemon
2017-12-19 20:19 ` bugzilla-daemon
2017-12-19 21:13 ` bugzilla-daemon
2017-12-20 10:44 ` bugzilla-daemon
2017-12-20 11:14 ` bugzilla-daemon
2018-01-18 18:43 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-196197-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).