FS#33994 - [xorg-server][nouveau-dri] X Server 1.13.2 crashes when starting Chromium
Attached to Project:
Arch Linux
Opened by Matteo Drera (seven.issimo) - Sunday, 24 February 2013, 11:52 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 March 2013, 16:22 GMT
Opened by Matteo Drera (seven.issimo) - Sunday, 24 February 2013, 11:52 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 March 2013, 16:22 GMT
|
Details
Description:
Xorg crashes every time I open a webpage in Chromium, probably due to (GPU?) render stack. Fresh Chromium profile doesn't solve issue. Disable/enable various Chromium GPU-related flags doesn't help. Additional info: * package version(s): - extra/xorg-server 1.13.2.901-1 (xorg) - extra/xf86-video-nouveau 1.0.6-1 (xorg-drivers xorg) - extra/chromium 25.0.1364.97-1 * config and/or log files etc. - Xorg.log Steps to reproduce: - Start Chromium on nvidia+nouveau hardware - Open a webpage 
Xorg.0.log.old
(30.2 KiB)
|
This task depends upon
Closed by Andreas Radke (AndyRTR)
Thursday, 14 March 2013, 16:22 GMT
Reason for closing: Fixed
Additional comments about closing: 9.1-3
Thursday, 14 March 2013, 16:22 GMT
Reason for closing: Fixed
Additional comments about closing: 9.1-3
I'm afraid I don't have access to an x86_64 machine at the moment to see if I can reproduce it there as well.
Additional info:
linux 3.8.2-1
xorg-server 1.13.2.901-1
xf86-video-nouveau 1.0.6-1
nouveau-dri 9.1-2
The culprits in my case seem to be Chromium 25 builds ( both Chromium 25.0.1364.97-1 and Chromium 25.0.1364.152-2 ).
This only happens on 25.x.x.x ... previous Chromium versions don't cause segfaults in X ( 24.x.x.x and earlier ).
I tested both Chromium 25 builds with :
1) current profile => immediate crash upon opening Chromium ( briefly window is seen ), then xorg-server segfaults, DM restarts.
2) brand new profile => same issue either immediately upon opening Chromium, or just once, not immediately --- but after going to menu.
In both cases the xorg-server log is almost identical to that of the OP.
It seems to indicate change(s) in Chromium 25 are causing this.
I have not made any changes in Chromium startup options, enabled experimental features, etc.
Maybe this observation might be useful.
For what I can find, this looks identical to what users are reporting on Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=862466#c15
That comment also debugs the problem and contains a possible fix. Can someone please test the attached patch? It's the same check that the intel DRI driver does, so it should be correct this way.
At the moment, the freedesktop.org servers are seemingly down .... so I couldn't retrieve the sources to recompile.
I did a quick experiment by moving nouveau_vieux_dri.so to a temp location and restarting the DM to force usage of llvmpipe.
With Gallium 0.4 on llvmpipe, I ran Chromium 25.0.1364.152-2 and it didn't crash the xorg-server. ( so far, so good )
I applied the patch posted by JGC, and recompiled.
Copied the nouveau_vieux_dri.so to /usr/lib/xorg/modules/dri/ .... and the issue seems to be fixed.
Granted, I haven't done extensive testing yet, but Chromium now seems to be back in business.
JGC, since this small patch seems to be non-invasive (and as you mentioned, in line with what Intel DRI does), would you consider
updating the nouveau_dri package?
https://bugs.freedesktop.org/show_bug.cgi?id=61947
Your patch was applied upstream to master, and it's also been marked as "stable candidate".