dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66972] GPU lockup CP stall with radeon.dpm=1 on BARTS/6850
Date: Tue, 16 Jul 2013 21:34:30 +0000	[thread overview]
Message-ID: <bug-66972-502-utDNGBfor4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66972-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3801 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=66972

--- Comment #4 from Andre Heider <a.heider@gmail.com> ---
Thanks, but with that patch and "radeon.dpm=1 radeon.aspm=0" I still get the
stall. And now lightdm just displays garbage, before the patch it was able to
come up after a delay.

Also, I noticed this "ACPI FADT declares the system doesn't support PCIe ASPM,
so disable it", related?

[   18.907265] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[   18.907271] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000003
last fence id 0x0000000000000001)
[   18.985214] radeon 0000:01:00.0: Saved 87 dwords of commands on ring 0.
[   18.985225] radeon 0000:01:00.0: GPU softreset: 0x00000008
[   18.985227] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0003828
[   18.985230] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[   18.985232] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[   18.985234] radeon 0000:01:00.0:   SRBM_STATUS               = 0x20000AC0
[   18.985236] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[   18.985238] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[   18.985241] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00004100
[   18.985243] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00020180
[   18.985245] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80028042
[   18.985247] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[   18.997899] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00004001
[   18.997952] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[   18.999099] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[   18.999101] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[   18.999103] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[   18.999106] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[   18.999108] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[   18.999110] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[   18.999112] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[   18.999114] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[   18.999116] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[   18.999118] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[   18.999125] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[   19.020762] [drm] PCIE gen 2 link speeds already enabled
[   19.022654] [drm] PCIE GART of 512M enabled (table at 0x0000000000273000).
[   19.022749] radeon 0000:01:00.0: WB enabled
[   19.022751] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff8807fff9fc00
[   19.022752] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff8807fff9fc0c
[   19.024253] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc9000c932118
[   19.040412] [drm] ring test on 0 succeeded in 3 usecs
[   19.040474] [drm] ring test on 3 succeeded in 1 usecs
[   19.215251] [drm] ring test on 5 succeeded in 2 usecs
[   19.215258] [drm] UVD initialized successfully.
[   19.217129] [drm] ib test on ring 0 succeeded in 0 usecs
[   19.217182] [drm] ib test on ring 3 succeeded in 1 usecs
[   29.368594] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[   29.368601] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000002)
[   29.368604] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
[   29.368610] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4597 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-07-16 21:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 17:40 [Bug 66972] New: GPU lockup CP stall with radeon.dpm=1 on BARTS/6850 bugzilla-daemon
2013-07-16 18:32 ` [Bug 66972] " bugzilla-daemon
2013-07-16 18:33 ` bugzilla-daemon
2013-07-16 20:49 ` bugzilla-daemon
2013-07-16 21:34 ` bugzilla-daemon [this message]
2013-07-17  1:43 ` bugzilla-daemon
2013-07-17 15:18 ` bugzilla-daemon
2013-07-17 16:40 ` 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-66972-502-utDNGBfor4@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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).