Red Hat Bugzilla – Bug 1259443
Add brw_meta_fast_clear crash workaround patch
Last modified: 2016-07-12 12:16:56 EDT
Description of problem: Would be nice to add the workaround patch posted at [1] to stop things from crashing with #5 0x00007fc5e76df64c in brw_meta_fast_clear () at /usr/lib64/dri/i965_dri.so #6 0x00007fc5e766c55c in brw_clear () at /usr/lib64/dri/i965_dri.so (if you are unlucky, some core KDE services also crash this way, taking down the entire session with them). According to [2], a proper fix will take time to land, so in the meantime, applying this would be nice (have been using the patch for a while, and things improved noticeably). [1] https://bugs.freedesktop.org/show_bug.cgi?id=86281#c39 [2] https://bugs.freedesktop.org/show_bug.cgi?id=86281#c44 Version-Release number of selected component (if applicable): mesa-11.1.0-0.devel.2.60aea30.fc24.x86_64 How reproducible: Pretty frequently during normal desktop use on Plasma 5 with Intel Gen3 (Ivy Bridge) graphics controller
I can confirm the named patch solved the problem for me on Fedora 22. I recompiled mesa-10.6.3-1.20150729.fc22.src.rpm with the patch and reinstalled mesa-dri-drivers-10.6.3-1.20150729.fc22.x86_64 . Plasma stopped crashing for now. This is rather urgent I would say since with a recent Fedora 22 update Plasma 5 is not barely usable (the time scale of the frequency of the crashes is in minutes, sometimes many times a minute). Plasma is not the only application affected, it is just one of the many. FYI the update introducing the bug in Fedora 22 seems to be: Upgraded xorg-x11-drv-intel-2.99.917-12.20150615.fc22.x86_64 @updates Upgrade 2.99.917-15.20150729.fc22.x86_64 @updates
*** Bug 1260382 has been marked as a duplicate of this bug. ***
*** Bug 1260395 has been marked as a duplicate of this bug. ***
See also, http://news.softpedia.com/news/critical-intel-graphics-driver-bug-puts-kde-plasma-5-in-a-really-bad-light-488621.shtml Unfortunate combination of bad timing, and recent xorg-x11-drv-intel apparently getting enough karma to skip -testing altogether: https://bodhi.fedoraproject.org/updates/FEDORA-2015-13944 In a constructive vein, any objection to including the workaround referenced in the upstream report? Direct reference here: http://cgit.freedesktop.org/~ickle/mesa/commit/?h=brw-batch&id=e2a696a4cd93c2dbe445243de48ed478fbdb8009
Can we get this bug fixed please? The patch is confirmed working, now lets get it released.
Per irc chat, <ignatenkobrain> rdieter: busy last time =( can you apply patch? So, I can help take care of it.
Proposed as a Blocker for 23-beta by Fedora user rdieter using the blocker tracking app because: Including this upstream workaround for common/frequent plasmashell crashes. Otherwise, yields a very bad experience, see also some publicity on the issue: http://news.softpedia.com/news/critical-intel-graphics-driver-bug-puts-kde-plasma-5-in-a-really-bad-light-488621.shtml which would be nice to avoid if at all possible
mesa-10.6.3-2.20150729.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543
mesa-11.0.0-0.rc2.2.20150902.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15544
F22-using folks who want to test this immediately: mkdir /tmp/whatever; cd /tmp/whatever koji download-build mesa-10.6.3-2.20150729.fc22 --arch=x86_64 --arch=i686 --arch=noarch sudo dnf upgrade *rpm
Discussed at 2015-09-10 freeze exception review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-09-10/f23-blocker-review.2015-09-10-16.00.log.txt . Accepted as a Beta blocker, as a conditional violation of criterion "No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional." (various parts of KDE's panel etc. may crash in many cases, it sounds like).
mesa-11.0.0-0.rc2.2.20150902.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mesa'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15544
mesa-10.6.3-2.20150729.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mesa'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543
> If you want to test the update, you can install it with > su -c 'yum --enablerepo=updates-testing update mesa'. Well, that will not work, because there is no package called "mesa" (it's only the SRPM's name). Try: yum-deprecated --enablerepo=updates-testing --advisory=FEDORA-2015-15543 update Unfortunately, it looks like dnf does not support that yet. I filed bug #1262572.
mesa-10.6.3-2.20150729.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
mesa-11.0.0-0.rc2.2.20150902.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Created attachment 1075948 [details] List of patches updated
After latest updates (see attached) looks like this bug came back.
Another user experienced a similar problem: I have just started the computer (laptop) and the displayport screen was powered on, when the boot process was already ongoing. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: ksplashqml Breeze --pid crash_function: brw_meta_fast_clear executable: /usr/bin/ksplashqml global_pid: 1924 kernel: 4.2.3-200.fc22.x86_64 package: plasma-workspace-5.4.2-4.fc22 reason: ksplashqml killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Created attachment 1088499 [details] File: backtrace
rpm -q mesa-libGL please.
Another user experienced a similar problem: When switching virtual desktops. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --graceTime 25051 --ksldfd 39 crash_function: brw_meta_fast_clear executable: /usr/libexec/kscreenlocker_greet global_pid: 7338 kernel: 4.2.7-200.fc22.x86_64 package: plasma-workspace-5.4.3-3.fc22 reason: kscreenlocker_greet killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1310405 has been marked as a duplicate of this bug. ***
*** Bug 1296632 has been marked as a duplicate of this bug. ***
*** Bug 1299598 has been marked as a duplicate of this bug. ***
*** Bug 1310211 has been marked as a duplicate of this bug. ***
*** Bug 1243741 has been marked as a duplicate of this bug. ***
*** Bug 1299310 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The screen went to lock the lock screen, I grabbed the mouse so I wouldn't have to type in my password, and the screen momentarily froze. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --graceTime 25000 --ksldfd 61 crash_function: brw_meta_fast_clear executable: /usr/libexec/kscreenlocker_greet global_pid: 30197 kernel: 4.4.13-200.fc22.x86_64 package: kscreenlocker-5.5.5-2.fc22 reason: kscreenlocker_greet killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: While logging in. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --graceTime 25000 --ksldfd 60 crash_function: brw_meta_fast_clear executable: /usr/libexec/kscreenlocker_greet global_pid: 10212 kernel: 4.4.13-200.fc22.x86_64 package: kscreenlocker-5.5.5-2.fc22 reason: kscreenlocker_greet killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000