[Bug 103726] GPU crashes freezing the system and weird rendering issues on CAYMAN

* [Bug 103726] GPU crashes freezing the system and weird rendering issues on CAYMAN
@ 2017-11-14  1:20 bugzilla-daemon
  2019-09-18 19:24 ` bugzilla-daemon
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2017-11-14  1:20 UTC (permalink / raw)
  To: dri-devel

[-- Attachment #1.1: Type: text/plain, Size: 2744 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103726

            Bug ID: 103726
           Summary: GPU crashes freezing the system and weird rendering
                    issues on CAYMAN
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: v10lator@myway.de
        QA Contact: dri-devel@lists.freedesktop.org

I'm not really sure how to describe this bug. It is so random, sometimes I'm
not sure if exists as nothing happens in weeks, then it happenes all 10
minutes. I'm hunting this bug for so long, can't tell if a year or two or even
more.

Some (if not all?) games are triggering weird behavior on a Radeon HD 6950.
What happens is the screen changing to green with some check pattern (sorry for
having no picture but screenshoting is impossible and I never had a camera at
hand). Before the driver was able to do a GPU reset (now you get how old this
bug is) it was staying there but with modern kernels the drivers seems to try a
reset (monitor flickering for a moment) after some time and then all I get is a
black screen (not no-signal, a black image) at that time the only way to
recover the PC is by pressing the reset button.

Now since a few days I'm playing Dead Island and it seems to be a good trigger
for the bug ("good" means the game seems to trigger it in between a few seconds
and 6 hours of gameplay. Make sure to have a lot of freetime if you try to
recreate) so I decided to try to hunt it again. For that I started the game
with R600_DEBUG=nosb,nohyperz and played for around 3 hours before I got bored.
Then I switched back to the desktop and noticed that everything got broken:
Flickering and/or invisible windows, hanging menue, the complete desktop
hanging and so on (I tried to take a video but it's corrupted: [ffmpeg/demuxer]
mov,mp4,m4a,3gp,3g2,mj2: moov atom not found) ).

When the desktio corruted there's nothing in the logs except
kernel: radeon_dp_aux_transfer_native: 32 callbacks suppressed
but that should be harmless, shouldn't it?

When the green screen comes there#s also nothing in the logs, but that's most
likely because the system froze before it could flush it to disc as the logs
are incomlete im that case.

This bug might or might not be the same as
https://bugs.freedesktop.org/show_bug.cgi?id=92555 - I really can't tell but if
it's the same: Could it be a regresion introduced by splitting r600 and
radeonsi?

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

[-- Attachment #1.2: Type: text/html, Size: 4294 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

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