Recently with mga4 it is rather easy to provoke crash in the i915 intel graphics - watching youtube videos with chromium browser frequently triggers it, so does loading openstreetmap driven maps. Symptoms are as follows: * screen goes black, even on virtual consoles * if you suspend and resume, display is shown again, however gnome-session fails and shows the "oh no, something went wrong" screen with the only option to log out. * ignore that and use virtual console to kill the gnome-session-failed process and run e.g. metacity --display=:0.0 --replace so you're able to gracefully shut down your apps/save your data, etc. * reboot, repeat... It's really annoying as the gnome failed screen disables all the gnome-shell extensions, and even with metacity as window manager, switching between windows fails via alt+tab fails in that recovered session (you can switch using mouse though) I think (not really sure about it), that https://bugs.freedesktop.org/show_bug.cgi?id=77104 is related/the cause of the problem It has a backport for 3.14 kernel attached, so I'd like to request a kernel update with that patch if possible. Reproducible: Steps to Reproduce:
What CPU / GPU do you have ?
CC: (none) => tmb
I've submitted a 3.14.25-1 to updates_testing with the fix "drm/i915: Disable RCS flips on Ivybridge"
thanks for the updated package, unfortunately my specific problem was not solved with that, filed a bug upstream https://bugs.freedesktop.org/show_bug.cgi?id=86972 It's mobile chipset GM965 $ lspcidrake -v |grep -i graphic unknown : Intel Corporation|Mobile GM965/GL960 Integrated Graphics Controller (secondary) [DISPLAY_OTHER] (vendor:8086 device:2a03 subv:1734 subd:110f) (rev: 03) Card:Intel 810 and later: Intel Corporation|Mobile GM965/GL960 Integrated Graphics Controller (primary) [DISPLAY_VGA] (vendor:8086 device:2a02 subv:1734 subd:110f) (rev: 03) $ grep -i -- --.*graphics /var/log/Xorg.0.log [ 11.985] (--) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
my upstream bug has been reassigned/reamed and with that info I could find a workaround for my problem. https://bugs.freedesktop.org/show_bug.cgi?id=80568#c62 - setting always_flush_cache=true does workaround the problem (at least couldn't reproduce anymore so far) I did put it in /etc/environment, so I don't need to think about it when launching the browser.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD