Bug #1099
Frequent X11 Fatal server errors (caught signal 11)
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
Hi,
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?
Regards,
Michael
Related todos
History
Updated by dillon almost 5 years ago
:Hi,
:
: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?
:
:Regards,
:
: Michael
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).
cd /usr/src/
make -j 16 buildworld
-Matt
Updated by corecode almost 5 years ago
Try switching off EXA and use XAA instead.
cheers
simon
Updated by mneumann almost 5 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
pkgsrc-wip.
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 :)
Regards,
Michael
Updated by nonsolosoft almost 5 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:
Section "Device"
[...]
Option "AccelMethod" "XAA"
EndSection
I've fixed in such way my problems.
Bye, \fer
Updated by tuxillo over 3 years ago
Hi Michael,
I've observed that this happened with Xorg version 1.3 which is quite old. Does
it still happen with 1.6.3?
Cheers,
Antonio Huete
Updated by tuxillo 2 months ago
- Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
0)
Hi,
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.
Cheers,
Antonio Huete