Frequent X11 Fatal server errors (caught signal 11)
X11 starts just fine, but after a while I always get a Fatal server
error (caught signal 11).
This happens with the intel driver. Xorg.0.log appended, together with
xorg.conf and dmesg.
Anything I can do about it? Any hints how to track down this bug?
#1 Updated by dillon over 9 years ago
:X11 starts just fine, but after a while I always get a Fatal server
:error (caught signal 11).
:This happens with the intel driver. Xorg.0.log appended, together with
:xorg.conf and dmesg.
:Anything I can do about it? Any hints how to track down this bug?
Hmm. If the server started fine and you weren't doing anything in
particular (like switching to a different virtual console) when it
failed, it could be an indication of a hardware problem.
A good test for memory / hardware problems is to run a big parallel
buildworld and see if it fails in random places (usually with an
internal compiler error or random seg-fault).
make -j 16 buildworld
#3 Updated by mneumann over 9 years ago
Thanks for your hints.
I don't know how to turn off EXA (I didn't even know what this acroym
stands for before looking at Wikipedia ;-). Nevertheless I fixed the
problem by switching to modular-xorg-server version 1.4.2 which is in
Only one problem is still left. When switching to console and back again
to X11, I can't use the X11 applications any more. Only a xorg server
restart helps. But that's a lot less worse than random signal 11's :)
#4 Updated by nonsolosoft over 9 years ago
I had some sort of same troubles on latest xorg update.
To check what is it:
uncomment Option "NoTrapSignals" from /usr/pkg/xorg/lib/X11/xorg.conf
and if it coredumps on libexa.so you can select XAA in your xorg.conf
in this way:
Option "AccelMethod" "XAA"
I've fixed in such way my problems.
#6 Updated by tuxillo almost 5 years ago
- Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
As pointed out by the caller, switching to Xorg 1.4.2 made the signal 11 problem go away. I can confirm I've used later Xorg versions with Intel driver without the described issues.