From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 81644] New: Random crashes on RadeonSI with Chromium.
Date: Tue, 22 Jul 2014 15:50:52 +0000
Message-ID:
Priority
medium
Bug ID
81644
Assignee
dri-devel@lists.freedesktop.org
Summary
Random crashes on RadeonSI with Chromium.
Severity
normal
Classification
Unclassified
OS
All
Reporter
aaronbottegal@gmail.com
Hardware
Other
Status
NEW
Version
git
Component
Drivers/Gallium/radeonsi
Product
Mesa
Chromium randomly crashes with RadeonSI driver when using Chromium. Most
usually with Youtube videos. Everything is current git from Oibaf PPA using
Mint 17 Cinnamon, although I'm about to move to Arch Linux so I don't know how
long I'll be able to provide logs as the problem doesn't exist in Arch's
currents AFAIK. But there are logs in Bug #77980 from my crash, which was close
sounding, but apparently a different bug.
What | Removed | Added |
---|---|---|
Hardware | Other | x86-64 (AMD64) |
Priority | medium | high |
(In reply to comment #1= ) > Everything is current git from Oibaf PPA using M= int 17 Cinnamon, although I'm > about to move to Arch Linux so I don't know how long I'll be able to p= rovide > logs as Better attach them here ASAP then. :) Xorg.0.log, dmesg and glxinfo. > the problem doesn't exist in Arch's currents AFA= IK. What version of Mesa does that use?
Created attachment 103414 [details]
DMesg
I have moved to Arch. Bug just happened and is in these logs. I'm currently on
Mesa-git. And the bug not being present isn't solid. My friend told me it
didn't happen, and has the same tower. But he didn't stay on it long enough to
happen so I'm going to take that back for now. I don't remember this bug in
Mesa from around January, but yet my card was unusable in January. So I'd ping
it to somewhere around 2-5 months old tbh. But yes, Chromium has this problem
on arch, and I switched not only OS's but DE's so it's not a Cinnamon problem.
Created attachment 103416 [details]
XOrg log, with crash+recover.
Created attachment 103417 [details]
Hardware report.
Important hardware:
R9 270X - 2GB GDDR5 - ASUS.
FX-8350 - AMD.
M5A99FX PRO 2.0 - ASUS.
What | Removed | Added |
---|---|---|
Attachment #103504 is obsolete | 1 |
Created attachment 103522 [details]
Two crashes+recovers. Xorg.
What | Removed | Added |
---|---|---|
Attachment #103505 is obsolete | 1 |
Created attachment 103523 [details]
Two crashes+recovers. Dmesg.
(In reply to comment #1) > (In reply to comment #1) > > Everything is current git from Oibaf PPA using Mint 17 Cinnamon, although I'm > > about to move to Arch Linux so I don't know how long I'll be able to provide > > logs as > > Better attach them here ASAP then. :) Xorg.0.log, dmesg and glxinfo. > > > the problem doesn't exist in Arch's currents AFAIK. > > What version of Mesa does that use? I'm guessing as of this patch this can be closed? http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2062afb4f804afef61cbe62a30cac9a46e58e067
(In reply to comment #= 11) > I'm guessing as of this patch this can be closed? > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git= /commit/ > ?id=3D2062afb4f804afef61cbe62a30cac9a46e58e067 No, that's unrelated. BTW, the backtraces in Xorg log files aren't useful for diagnosing this kin= d of problem, so there's no point in attaching more Xorg log files just for that= .
(In reply to comment #6= ) > Chromium randomly crashes with RadeonSI driver w= hen using Chromium. Most > usually with Youtube videos. Using Flash or HTML5 video? Fullscreen or windowed? ...
(In reply to comment #13) > (In reply to comment #6) > > Chromium randomly crashes with RadeonSI driver when using Chromium. Most > > usually with Youtube videos. > > Using Flash or HTML5 video? Fullscreen or windowed? ... I use HTML5 video. But it's a Chromium issue in general, flash video just helps it happen faster. It also happens a lot when switching tabs, clicking on content that adds a new element on the page over top of everything else, or loading more objects. Good examples are opening the comments section on Yahoo, and the mousing over of names on facebook. Think it'd be useful to try to attach a gdb session to Chromium? In the dmesg log, every time the problem happens, Chromium does receive a segfault.
(In reply to comment #= 14) > I use HTML5 video. But it's a Chromium issue in = general, flash video just > helps it happen faster. Is it HTML5 or Flash now? :) > Think it'd be useful to try to attach a gdb sess= ion to Chromium? In the dmesg > log, every time the problem happens, Chromium does receive a segfault.= Yes, backtraces of those crashes might be interesting.
(In reply to comment #15) > (In reply to comment #14) > > I use HTML5 video. But it's a Chromium issue in general, flash video just > > helps it happen faster. > > Is it HTML5 or Flash now? :) > > > > Think it'd be useful to try to attach a gdb session to Chromium? In the dmesg > > log, every time the problem happens, Chromium does receive a segfault. > > Yes, backtraces of those crashes might be interesting. Whoops, I meant the video playing in HTML5 made the glitch happen worse. But it's video in general, Flash video on other sites does crash it too. And okay, if I can get it working I'll hopefully have a good log to show sooner or later.
I just got a crash while trying to get some debugging output...but all Chromium would output, and it was just through the terminal, was "GPU process stalled after 10000ms." and that was basically all the information I got from it. I'll try again tomorrow, maybe try valgrind or some different CL arguments this time around. We'll see. Now it's time for sleep, though.
so I got a different bug or could this be the same ? running on drm-next-3.17-rebased-on-fixes only doing some surfing via current opera-developer (https://bugs.gentoo.org/show_bug.cgi?id=514696) flash plugin was not working (tested via surfing over to speedtest.net) switched a few times between KDE4, fluxbox, xfce4 and razor-qt window managers were compiz-fusion (0.8.8/0.8.6), kwin with opengl compositing (opengl 1.2, 2.0, 3.1 testing) programs used: - gnote, tomboy - opera-developer - firefox (flash rendered unusable by uninstalling vdpau, no data via env VDPAU_TRACE=1 firefox), noscript, adblock (these were all if I remember correctly) first hardlock (no Magic SYSRQ Key recovery possible) was during playing around and switching between Themes in Opera Developer (version 24) second hardlock was during simply reading a few notes in gnote and surfing via firefox (version 31)
It sounds like the same bug, but I'm not 1000% sure. But I had a few crashes in Chromium, the only out of place log message is: ATTENTION: default value of option force_s3tc_enable overridden by environment. [8923:8923:0731/125646:ERROR:sandbox_linux.cc(302)] InitializeSandbox() called with multiple threads in process gpu-process Not what to make of it, but it's something more.
[7925:7960:0731/125644:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms. [7894:7894:0731/125644:ERROR:gpu_process_transport_factory.cc(347)] Lost UI shared context. Here also is the message about the process hanging, it was in the log too, missed it at first.
I'm getting the glitch a lot more, but trying to remember what sets it off most: 1. Youtube. Often, but not as often as #2. 2. Clicking on an element that brings up another element onto the page, basically over it with a higher z-index, like I said facebook does this a LOT. 3. Adding elements to the page at all can also trigger this bug. Like loading ANY comments, from disqus to yahoo, they all have triggered it. 4. Slideshows where the objects slide against each other, like in PCWorld slideshows, just had a crash there. All of these have in common is moving pixels, but also adding pixels to the screen. Is there special code for that, those dirty rectangles being glitchy or something? I have, well, only bare minimal knowledge of how these drivers work from looking at lots of Git commits, but I bet that is a pretty good clue to people who know what they're looking at with what could be wrong. :)