From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 68125] New: Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression) Date: Wed, 14 Aug 2013 23:07:17 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0957844240==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B6F61E5D2B for ; Wed, 14 Aug 2013 16:07:17 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0957844240== Content-Type: multipart/alternative; boundary="1376521637.30844d0.12164"; charset="us-ascii" --1376521637.30844d0.12164 Date: Wed, 14 Aug 2013 23:07:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=68125 Priority: medium Bug ID: 68125 Assignee: dri-devel@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@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. --1376521637.30844d0.12164 Date: Wed, 14 Aug 2013 23:07:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
Priority medium
Bug ID 68125
Assignee dri-devel@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@debian.org
Hardware x86-64 (AMD64)
Status NEW
Version XOrg CVS
Component DRM/Radeon
Product DRI 

Created attachment 84074 [details]
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.
--1376521637.30844d0.12164-- --===============0957844240== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0957844240==--