[Bug 75841] New: radeon (radeonsi): GPU crash and resulting kernel problems (hangs etc.)

* [Bug 75841] New: radeon (radeonsi): GPU crash and resulting kernel problems (hangs etc.)
@ 2014-05-10  1:31 bugzilla-daemon
  2014-05-10  1:54 ` [Bug 75841] " bugzilla-daemon
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-05-10  1:31 UTC (permalink / raw)
  To: dri-devel

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

            Bug ID: 75841
           Summary: radeon (radeonsi): GPU crash and resulting kernel
                    problems (hangs etc.)
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.15-rc3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: bugspam@moreofthesa.me.uk
        Regression: No

Created attachment 135651
  --> https://bugzilla.kernel.org/attachment.cgi?id=135651&action=edit
Partial kernel log showing many GPU faults and subsequent page table breakage

I'm reliably able to trigger GPU faults and various subsequent problems. The
crash doesn't happen immediately, so far as I can tell.

One known trigger is to start a map then start another map on Unvanquished
(http://www.unvanquished.net/). It appears that the heat haze option needs to
be enabled (this one seems most reliable), and I think that the motion blur
option may also trigger this.

Known effects, other than reams of GPU fault reports, include hard lock-ups and
page table corruption; the attached file (gpu-crash-etc.txt) shows the latter
(I chose to reboot soon afterwards).

Hardware is Bonaire XTX. Userland is X git (2535b76) with corresponding Radeon
DDX, Mesa 10.2 git (e05ceba, built using xorg-edgers packaging), llvm 3.4-2
(Debian). GLAMOR is enabled.

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

^ permalink raw reply	[flat|nested] 8+ messages in thread