From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42678] [3.3-rc1] radeon stuck in kernel after lockup
Date: Wed, 1 May 2013 17:50:14 +0000 (UTC) [thread overview]
Message-ID: <20130501175014.AAC3F11FF43@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42678-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42678
Laurent Bonnaud <Laurent.Bonnaud@inpg.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Laurent.Bonnaud@inpg.fr
--- Comment #21 from Laurent Bonnaud <Laurent.Bonnaud@inpg.fr> 2013-05-01 17:50:14 ---
This bug is still present in Ubuntu raring with this kernel package:
Package: linux-image-3.8.0-19-generic
Version: 3.8.0-19.29
which is based on kernel 3.8.8.
The GPU did hang a few times and the kernel was able to recover. But later the
kernel was caught in an infinite loop of GPU hangs and I was not able to take
back the control of the X server and therefore I lost unsaved work in my X
session. Between 2 hangs I was able to switch to a VT and run dmesg, so here
is the end of the kernel log:
[73670.536108] radeon 0000:01:00.0: GPU lockup CP stall for more than 10168msec
[73670.536200] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000c7f78)
[73670.536203] radeon 0000:01:00.0: failed to get a new IB (-35)
[73670.536255] [drm:radeon_cs_ib_chunk] *ERROR* Failed to get ib !
[73670.537377] radeon 0000:01:00.0: Saved 1017 dwords of commands on ring 0.
[73670.537380] radeon 0000:01:00.0: GPU softreset: 0x00000003
[73670.691016] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA27034E0
[73670.691018] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000103
[73670.691021] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200200C0
[73670.691023] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000
[73670.691025] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00001002
[73670.691027] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00028C86
[73670.691030] radeon 0000:01:00.0: R_008680_CP_STAT = 0x808386C5
[73670.691032] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE
[73670.705914] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
[73670.720796] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA0003030
[73670.720799] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000003
[73670.720801] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200280C0
[73670.720803] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[73670.720805] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[73670.720808] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[73670.720810] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80100000
[73670.731190] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[73670.748806] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
[73670.920570] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[73670.920609] radeon 0000:01:00.0: WB enabled
[73670.920612] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000010000c00 and cpu addr 0xffff8801347e0c00
[73670.920614] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000010000c0c and cpu addr 0xffff8801347e0c0c
[73671.118349] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xCAFEDEAD)
[73671.118480] [drm:r600_resume] *ERROR* r600 startup failed on resume
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-05-01 17:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 15:16 [Bug 42678] New: [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2012-01-28 15:16 ` [Bug 42678] " bugzilla-daemon
2012-01-28 18:27 ` [Bug 42678] [3.3-rc1] radeon stuck in kernel after lockup bugzilla-daemon
2012-01-29 20:31 ` bugzilla-daemon
2012-02-04 8:39 ` bugzilla-daemon
2012-02-06 22:11 ` bugzilla-daemon
2012-02-07 6:59 ` bugzilla-daemon
2012-02-23 22:32 ` bugzilla-daemon
2012-02-24 2:53 ` bugzilla-daemon
2012-02-24 8:42 ` bugzilla-daemon
2012-03-29 22:07 ` bugzilla-daemon
2012-03-29 22:57 ` bugzilla-daemon
2012-04-03 19:38 ` bugzilla-daemon
2012-04-03 21:24 ` bugzilla-daemon
2012-04-04 12:43 ` bugzilla-daemon
2012-05-03 11:17 ` bugzilla-daemon
2012-05-04 8:10 ` bugzilla-daemon
2012-05-04 12:50 ` bugzilla-daemon
2012-05-04 13:04 ` bugzilla-daemon
2012-05-04 13:08 ` bugzilla-daemon
2012-05-04 14:21 ` bugzilla-daemon
2012-05-04 17:27 ` bugzilla-daemon
2013-05-01 17:50 ` bugzilla-daemon [this message]
2013-07-12 20:13 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2012-02-23 22:51 3.3-rc4+: Reported regressions from 3.2 Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-02-24 9:14 ` Torsten Kaiser
2012-02-24 9:14 ` Torsten Kaiser
2012-03-04 20:29 3.3-rc6: Reported regressions from 3.2 Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-03-04 20:31 ` Rafael J. Wysocki
2012-03-11 21:23 3.3-rc7: Reported regressions from 3.2 Rafael J. Wysocki
2012-03-11 21:23 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-03-11 21:23 ` Rafael J. Wysocki
2012-03-12 19:15 ` Torsten Kaiser
2012-03-12 19:15 ` Torsten Kaiser
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=20130501175014.AAC3F11FF43@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.