Driver crash while playing YouTube video (flash)
Submitted by nuc..@..il.com
Assigned to Default DRI bug account
Description
Created attachment 100782
crash log
While watching a YouTube video (flash player) I experienced a driver crash, the monitor went black but recovered.
I attached the error log of the radeon driver.
Attachment 100782, "crash log":
radeon-log
Activity
Attachment 100817, "dmesg":
dmesgAttachment 100818, "Xorg.0.log":
Xorg.0.log
It just happened again with the same video: http://www.youtube.com/watch?v=d-Cc6j2ZBwk in 360p, firefox.
I don't know if I use UVD, but I don't think so (I guess this would require hw accelaration through gstreamer, but I don't have the corresponding packages installed).Appears the bug is independent of UVD enabled or not.
At least with UVD enabled I have got an additional error in dmseg:
[ 236.334117] radeon 0000:0b:00.0: GPU fault detected: 146 0x0ee6480c
[ 236.334121] radeon 0000:0b:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000010F7
[ 236.334123] radeon 0000:0b:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0604800C
[ 236.334126] VM fault (0x0c, vmid 3) at page 4343, read from 'TC2' (0x54433200) (72)Now this is interesting:
Only compton and compiz are affected by this bug.
I tested it with Kwin and xfwm4 with compositing enabled but it just doesn't happen. Also this bug can only be reproduced once - after that I need to restart my PC to trigger it (relogin is not enough).
Hope this was helpful.
@agd5fsubmitted a patch:Does this kernel patch help?
Patch 100841, "possible fix":
0001-drm-radeon-cik-soft-reset-the-CP-when-initializing-t.patchThanks, I will try the patch!
In case somebody has my graphics card (or a HD 7790 or maybe others too??) I found a definite and easy way to reproduce it:
- Start a lightweight DE with e.g. openbox or xfwm4 (compositing disabled)
- Install and start "compton" from a terminal
- Play this youtube video from firefox with flashplayer: http://www.youtube.com/watch?v=d-Cc6j2ZBwk (happens on others too, but this video is definately affected)
- The bug should occur in less than 1:30 minutes
- If it doesn't occur the first time just reload
This should definitely trigger the bug.- Start a lightweight DE with e.g. openbox or xfwm4 (compositing disabled)
Nope, unfortunately it doesn't help :/
I also get the bug on other occasions e.g. when I leave the PC and meanwhile the screensaver starts, I mostly find my computer in in a frozen state when I come back and need to do a hard reset. My journal is spammed by those same error messages then, until the journal log is full and stops logging...Ok some updates:
- I do not notice any difference with the patch or without
2. In contrary to my prior statements this bug is reproducable on any DE (even openbox) and is independent of compositing being enabled or not (although my impression is that it's easier to reproduce with compositing enabled).
3. It's independent or VDPAU.
4. It happens on any flash video, even on low quality.
5. Apart from playing flash videos the bug also happens on other (random) occasions or when the screensaver is active.
6. The system mostly successfully recovers from the crash *unless* a video is played in fullscreen (same for screensavers).
7. Out of some reason, it only happens *once* every restart. After the crash, I can successfully use my system and watch videos without any further crashes.
8. It's extremely annoying. I switched to Windows for the time being.- I do not notice any difference with the patch or without
Ok, I think the Heading is not really correct anymore. I'm on Linux 3.16.1 now and still get this misbehaviour even without watching yt videos (maybe because of some KDE effects).
It is extremely annoying and I basically cannot use Linux productively. In fact I am not even sure if this is a software issue. I also got some Problems on Windows with this card even though this is already my second one (from RMA).
And I am not the only one having issues. In fact, everybody using OC versions of the R7 260x has severe issues. It's a shame. The first company so far solving it was ASUS: They updated the firmware and it appears they just reduced the GPU clock and voltages.
Also see http://vip.asus.com/forum/view.aspx?id=20140427164821450&board_id=9&model=R7260X-DC2OC-2GD5&page=1&SLanguage=en-us
Sapphire also updated their firmware. MSI appears to don't care.
I don't know if this is related, but considering the poor state even on Windows, one never knows...This issue hasn't had any activity since 2019-11-19. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.
