[Bug 68125] New: Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Aug 14 16:07:17 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=68125
Priority: medium
Bug ID: 68125
Assignee: dri-devel at lists.freedesktop.org
Summary: Radeon HD6950: Failed to parse relocation -35 (Linux
3.11-rc regression)
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: aeb at debian.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 84074
--> https://bugs.freedesktop.org/attachment.cgi?id=84074&action=edit
Linux 3.11-rc5 dmesg
After running in X for a while, I get a monitor signal dropout for a few
seconds and find the follow messages in the kernel log:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Messages about the reset procedure, ring test etc. follow, with different
possible more or less successful recovery scenarios and messages playing out on
different occurences. Usually the second occurence kills X and further attempts
at logging in either end up in GNOME fallback mode or simply die immediately,
leaving only a reboot to solve the problem. With one run in 3.11-rc5 at least
it always recovered, reducing the impact of the bug to the occasional annoying
black screen for a few seconds.
This never happened before and never happens in Linux 3.10. The first kernel in
the 3.11 development cycle was 3.10.0-08918-g8133633, which already showed this
problem.
I'm running Debian unstable, xorg is 7.7, xserver-xorg-video-radeon 6.14.4,
libdrm-radeon1 2.4.46, mesa 9.1.6.
I have attached the log of the 3.11-rc5 which has plenty of these occurences
thanks to always recovering successfully.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130814/9e58554c/attachment.html>
More information about the dri-devel
mailing list