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 71864] [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
Date: Sun, 24 Nov 2013 16:17:56 +0000	[thread overview]
Message-ID: <bug-71864-502-NqHAQjdmrM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71864-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from reimth@gmail.com ---
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #12)
> > > (In reply to comment #11)
> > > > (In reply to comment #10)
> > > > > Is this still an issue with a newer kernel?  Did you also update your
> > > > > userspace stack (mesa, xf86-video-ati)?
> > 
> > Bad news: I confirm this bug also on linux kernel 3.8:
> > 

Current situation with kernel 3.8 seems to be worse than with kernel 3.2. It's
almost impossible to use the desktop. As soon as we work on Cinnamon (e. g.
Firefox), the system freezes latest after about 5 min. On the other hand, the
process between GPU lockup and final kernel oops has slightly changed. It takes
longer time until the kernel freezes. In the following there are two more
netconsole logs:
a) Late Kernel Freeze:
[80933.891948] radeon: wait for empty RBBM fifo failed ! Bad things might
happen.
[80934.031367] Failed to wait GUI idle while programming pipes. Bad things
might happen.
[80934.046827] radeon 0000:01:05.0: Saved 699 dwords of commands on ring 0.
[80934.046985] radeon 0000:01:05.0: (rs600_asic_reset:401)
RBBM_STATUS=0x9401C100
[80934.545149] radeon 0000:01:05.0: (rs600_asic_reset:421)
RBBM_STATUS=0x9401C100
[80935.042219] radeon 0000:01:05.0: (rs600_asic_reset:429)
RBBM_STATUS=0x9400C100
[80935.539290] radeon 0000:01:05.0: (rs600_asic_reset:437)
RBBM_STATUS=0x9400C100
[80935.539341] radeon 0000:01:05.0: failed to reset GPU
[80935.547414] radeon 0000:01:05.0: GPU reset failed
[80935.547563] radeon 0000:01:05.0: couldn't schedule ib
[80935.547569] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[80935.548226] radeon 0000:01:05.0: couldn't schedule ib
[80935.548241] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[80935.556425] radeon 0000:01:05.0: couldn't schedule ib
[80935.556442] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[80936.548449] radeon 0000:01:05.0: couldn't schedule ib

...

[86038.776434] radeon 0000:01:05.0: couldn't schedule ib
[86038.776464] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[86039.057988] radeon 0000:01:05.0: couldn't schedule ib
[86039.058017] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[86039.780421] radeon 0000:01:05.0: couldn't schedule ib
[86039.780450] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !

b) Magic Key Reboot before Actual Kernel Freeze
[ 1875.636067] radeon 0000:01:05.0: GPU lockup CP stall for more than 10000msec
[ 1875.636099] radeon 0000:01:05.0: GPU lockup (waiting for 0x0000000000001602
last fence id 0x0000000000001601)
[ 1875.776768] radeon: wait for empty RBBM fifo failed ! Bad things might
happen.
[ 1875.917215] Failed to wait GUI idle while programming pipes. Bad things
might happen.
[ 1875.925493] radeon 0000:01:05.0: Saved 379 dwords of commands on ring 0.
[ 1875.938200] radeon 0000:01:05.0: (rs600_asic_reset:401)
BBM_STATUS=0x9011C100
[ 1876.436314] radeon 0000:01:05.0: (rs600_asic_reset:421)
BBM_STATUS=0x90010140
[ 1876.933384] radeon 0000:01:05.0: (rs600_asic_reset:429)
BBM_STATUS=0x10000140
[ 1877.430455] radeon 0000:01:05.0: (rs600_asic_reset:437)
BBM_STATUS=0x10000140
[ 1877.430502] radeon 0000:01:05.0: GPU reset succeed
[ 1877.431503] radeon 0000:01:05.0: GPU reset succeeded, trying to resume
[ 1877.432008] [sched_delayed] sched: RT throttling activated
[ 1877.541132] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[ 1877.546610] [drm] PCIE GART of 512M enabled (table at 0x0000000036280000).
[ 1877.546690] radeon 0000:01:05.0: WB enabled
[ 1877.546697] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr
0x0000000080000000 and cpu addr 0xffff880036274000
[ 1877.546723] [drm] radeon: ring at 0x0000000080001000
[ 1877.684422] [drm:r100_ring_test] *ERROR* radeon: ring test failed
(scratch(0x15E8)=0xCAFEDEAD)
[ 1877.684426] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
[ 1877.684430] radeon 0000:01:05.0: failed initializing CP (-22).
[ 1953.942015] SysRq : 
 set to system default
[ 1954.772761] SysRq : 
 Tasks
[ 1954.817276] init: upstart-udev-bridge main process ended, respawning
[ 1954.817698] init: upstart-socket-bridge main process ended, respawning

...

[ 1955.395903] init: dbus main process ended, respawning
[ 1955.402682] init: mysql main process ended, respawning
[ 1955.444430] SysRq : 

...

[ 1955.614015] init: Disconnected from system bus
[ 1955.756307] init: plymouth-upstart-bridge main process (8471) terminated
with status 1
[ 1959.555121] SysRq : 
[ 1960.080595] Emergency Sync complete
[ 1962.056342] SysRq : 
[ 1962.139938] EXT4-fs (sdb1): re-mounted. Opts: (null)
[ 1962.192168] EXT4-fs (sda1): re-mounted. Opts: (null)
[ 1962.219457] EXT4-fs (sda2): re-mounted. Opts: (null)
[ 1962.232572] EXT4-fs (sdb10): re-mounted. Opts: (null)
[ 1962.378780] EXT4-fs (sdb7): re-mounted. Opts: (null)
[ 1962.384871] EXT4-fs (sdb8): re-mounted. Opts: (null)
[ 1962.385193] EXT4-fs (sdb9): re-mounted. Opts: (null)
[ 1962.386199] Emergency Remount complete
[ 1965.248738] SysRq : 
Resetting

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

[-- Attachment #1.2: Type: text/html, Size: 6242 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-11-24 16:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  8:42 [Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) bugzilla-daemon
2013-11-21  8:44 ` [Bug 71864] " bugzilla-daemon
2013-11-21  8:44 ` bugzilla-daemon
2013-11-21  8:45 ` bugzilla-daemon
2013-11-21  8:45 ` bugzilla-daemon
2013-11-21  8:50 ` bugzilla-daemon
2013-11-21  8:51 ` bugzilla-daemon
2013-11-21  8:55 ` bugzilla-daemon
2013-11-21  8:56 ` bugzilla-daemon
2013-11-21  9:00 ` bugzilla-daemon
2013-11-21 16:10 ` bugzilla-daemon
2013-11-22 14:49 ` bugzilla-daemon
2013-11-22 15:08 ` bugzilla-daemon
2013-11-23 11:39 ` bugzilla-daemon
2013-11-23 21:41 ` bugzilla-daemon
2013-11-24 15:37 ` bugzilla-daemon
2013-11-24 16:17 ` bugzilla-daemon [this message]
2013-11-24 17:15 ` bugzilla-daemon
2013-12-02 10:00 ` bugzilla-daemon
2013-12-02 17:55 ` bugzilla-daemon
2013-12-05 10:23 ` bugzilla-daemon
2013-12-05 15:10 ` bugzilla-daemon
2019-11-19  8: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-71864-502-NqHAQjdmrM@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).