dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66981] New: radeon 7970M, skyrim with mesa git: "GPU fault detected: 146"
Date: Sat, 14 Dec 2013 13:56:02 +0000	[thread overview]
Message-ID: <bug-66981-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=66981

            Bug ID: 66981
           Summary: radeon 7970M, skyrim with mesa git: "GPU fault
                    detected: 146"
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13-rc2
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: haagch.christoph@googlemail.com
        Regression: No

Created attachment 118371
  --> https://bugzilla.kernel.org/attachment.cgi?id=118371&action=edit
systemd journal/dmesg

muxless hybrid graphics

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wimbledon XT [Radeon HD 7970M]

dpm enabled, runpm disabled.

Software: xorg server 1.14.5, xf86-video-ati git d571d6a, glamor git 71e7168,
llvm svn 197173, mesa git 40070e7.

So I'm not sure whether to report this to mesa or the kernel, but I decided for
the kernel because it causes some errors there.

Playing skyrim in wine 1.7.8 with mesa git 00faf82 was working fine. mesa git
40070e7 introduced some rendering errors, but the thing here is that after a
while the gpu locks up and if I'm lucky it recovers and I simply can not render
anything anymore on the radeon gpu and if I'm unlucky I get a hard lockup of
the whole machine.

Important parts for people who google this:

Dez 14 14:07:12 c-l kernel: radeon 0000:01:00.0: GPU lockup CP stall for more
than 10000msec
Dez 14 14:07:12 c-l kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000025e0a5 last fence id 0x000000000025e0a4 on ring 0)
Dez 14 14:07:12 c-l kernel: radeon 0000:01:00.0: failed to get a new IB (-35)
Dez 14 14:07:12 c-l kernel: [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib !

and

Dez 14 14:07:15 c-l kernel: VM fault (0x00, vmid 0) at page 0, read from
unknown (0)
Dez 14 14:07:15 c-l kernel: radeon 0000:01:00.0: GPU fault detected: 146
0x0b06550c
Dez 14 14:07:15 c-l kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Dez 14 14:07:15 c-l kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

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

             reply	other threads:[~2013-12-14 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 13:56 bugzilla-daemon [this message]
2013-12-14 22:22 ` [Bug 66981] radeon 7970M, skyrim with mesa git: "GPU fault detected: 146" bugzilla-daemon
2013-12-14 23:32 ` bugzilla-daemon
2013-12-18  2:23 ` bugzilla-daemon
2013-12-18 13:52 ` bugzilla-daemon
2013-12-19 18:27 ` 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-66981-2300@https.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 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).