dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68059] with radeon.dpm=1,  Xorg crashed a while after resume
Date: Tue, 13 Aug 2013 22:11:06 +0000	[thread overview]
Message-ID: <bug-68059-502-2RcxRxbYTP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68059-502@http.bugs.freedesktop.org/>


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

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

wuruxu <wrxzzj@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |high

--- Comment #1 from wuruxu <wrxzzj@gmail.com> ---
[  119.444071] ata1.00: configured for UDMA/100
[  119.444305] sd 0:0:0:0: [sda] Starting disk
[  119.609043] usb 3-1: reset low-speed USB device number 2 using ohci-pci
[  129.095668] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec
[  129.095677] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000002)
[  129.095684] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
[  129.115566] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).
[  129.115570] [drm] Found smc ucode version: 0x00010601
[  129.116525] switching from power state:
[  129.116528]  ui class: none
[  129.116530]  internal class: boot
[  129.116531]  caps:
[  129.116535]  uvd    vclk: 0 dclk: 0
[  129.116538]    power level 0    sclk: 20000 vddc: 975
[  129.116540]  status: c b
[  129.116541] switching to power state:
[  129.116543]  ui class: performance
[  129.116544]  internal class: none
[  129.116545]  caps:
[  129.116546]  uvd    vclk: 0 dclk: 0
[  129.116548]    power level 0    sclk: 27827 vddc: 900
[  129.116549]    power level 1    sclk: 49231 vddc: 975
[  129.116551]  status: r
[  130.954614] PM: resume of devices complete after 12023.475 msecs

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

[-- Attachment #1.2: Type: text/html, Size: 2920 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

  reply	other threads:[~2013-08-13 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 13:22 [Bug 68059] New: with radeon.dpm=1, Xorg crashed a while after resume bugzilla-daemon
2013-08-13 22:11 ` bugzilla-daemon [this message]
2014-01-27 22:52 ` [Bug 68059] " bugzilla-daemon
2014-01-27 22:55 ` bugzilla-daemon
2014-01-27 22:56 ` bugzilla-daemon
2014-05-02 15:30 ` bugzilla-daemon
2015-10-21  0:18 ` bugzilla-daemon
2015-10-21  0:19 ` bugzilla-daemon
2015-10-21  0:20 ` bugzilla-daemon
2015-10-21  0:26 ` bugzilla-daemon
2015-10-21 14:59 ` bugzilla-daemon
2015-12-08  1:29 ` bugzilla-daemon
2018-04-10 10:52 ` bugzilla-daemon
2018-09-09 23:13 ` bugzilla-daemon
2018-09-10 14:42 ` bugzilla-daemon
2019-11-19  8:37 ` 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-68059-502-2RcxRxbYTP@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