When using low security settings with grsec, the X11 server will be killed after the intel DRI driver fails to recognize the PCI ID of the intel video card (bug #221111 includes a fix to get the PCI ID added to Mesa). I reported this firs at http://bugs.freedesktop.org/show_bug.cgi?id=14395 : """ grsec: signal 11 sent to /usr/bin/Xorg[X:13023] uid/euid:0/0 gid/egid:0/0, parent /usr/bin/xinit[xinit:13022] uid/euid:0/0 gid/egid:0/0 grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /usr/bin/Xorg[X:13023] uid/euid:0/0 gid/egid:0/0, parent /usr/bin/xinit[xinit:13022] uid/euid:0/0 gid/egid:0/0 gdb is being annoying and not letting me attach to the process in order to get a usable backtrace to see where that's coming from, and I'm not sure why... really frustrating. """ Starting X after 'export RLIMIT_CORE=4096' is a workaround... but I'd like to figure out where this is actually coming from, and gdb is being annoying. It's not attaching to the process for me to get a backtrace, and I can't figure out why. It looks like it's just hung (I don't see the normal "Reading symbols ........." progress).
> grsec: signal 11 sent to /usr/bin/Xorg[X:13023] uid/euid:0/0 gid/egid:0/0, > parent /usr/bin/xinit[xinit:13022] uid/euid:0/0 gid/egid:0/0 > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against > limit 0 for /usr/bin/Xorg[X:13023] uid/euid:0/0 gid/egid:0/0, parent > /usr/bin/xinit[xinit:13022] uid/euid:0/0 gid/egid:0/0 > A message like this is typically grsec simply recording that process receiving a signal 11, not it actually doing the killing. When the process died it tried to dump a core but grsec did deny that. Please post your emerge --info, kernel config and /var/log/Xorg.0.log
/var/log/Xorg.0.log is upstream... There was no useful info there, since I couldn't get gdb to attach. I'll get a core dump and analyze it next time I can. Thanks for the info on the grsec side of things.
http://wiki.x.org/wiki/Development/Documentation/ServerDebugging might be useful, if you haven't seen it already.
Reassigning to herd since eradicator has left Gentoo.
Bug is long fixed. Check freedesktop.org bug linked in the original post. Closing as FIXED.
