From: Remy Blank <remy.blank@pobox.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] xorg segfaults if I have an encrypted volume mounted
Date: Fri, 25 Jun 2010 00:53:49 +0200 [thread overview]
Message-ID: <i00nml$s68$1@dough.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2932 bytes --]
xorg started segfaulting here on startup, at the point where it should
detect input devices:
[ 1198.330] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1198.330] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1198.330] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 1198.330] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
objects
[ 1198.330] (II) AIGLX: Loaded and initialized /usr/lib/dri/i965_dri.so
[ 1198.330] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1198.331] (II) intel(0): Setting screen physical size to 507 x 317
[ 1198.437]
Backtrace:
[ 1198.437] 0: /usr/bin/X (xorg_backtrace+0x38) [0x80ae1c8]
[ 1198.437] 1: /lib/libudev.so.0 (0xb782b000+0x33d2) [0xb782e3d2]
[ 1198.437] Segmentation fault at address 0x7974702f
[ 1198.437]
Fatal server error:
[ 1198.437] Caught signal 11 (Segmentation fault). Server aborting
For reference, here's the same location in a good start:
[ 2832.766] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2832.766] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2832.766] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 2832.766] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
objects
[ 2832.766] (II) AIGLX: Loaded and initialized /usr/lib/dri/i965_dri.so
[ 2832.766] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2832.767] (II) intel(0): Setting screen physical size to 507 x 317
[ 2832.906] (II) config/udev: Adding input device Video Bus
(/dev/input/event8)
[ 2832.906] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 2832.906] (**) Video Bus: Applying InputClass "Keyboard-all"
[ 2832.906] (II) LoadModule: "evdev"
[ 2832.906] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2832.906] (II) Module evdev: vendor="X.Org Foundation"
[ 2832.906] compiled for 1.8.1.901, module version = 2.3.2
[ 2832.907] Module class: X.Org XInput Driver
[ 2832.907] ABI class: X.Org XInput driver, version 9.0
So it's segfaulting in libudev. And where it's getting weird is that it
only segfaults if I have one particular encrypted container mapped. The
container is a file mapped to /dev/loop0, opened with "cryptsetup
luksOpen" as "/dev/mapper/crypt-morpheus.athome". If I "luksClose" it
(but keep /dev/loop0), xorg starts normally.
Strangely, there is another encrypted container "/dev/mapper/crypt-swap"
mapped to my swap partition, but that one doesn't seem to interfere.
This symptom has only started today, and I haven't updated anything
udev- or xorg-related. However, I reboot rarely, and I did reboot today,
so it may be due to an earlier update.
Some version info:
xorg-server-1.8.1.901
xf86-input-evdev-2.3.2
udev-149
gentoo-sources-2.6.31-r6
Has anyone seen anything similar? Any idea how I could either work
around the issue or debug it? I have tried strace but couldn't extract
any meaningful information.
-- Remy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-06-24 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 22:53 Remy Blank [this message]
2010-06-25 12:52 ` [gentoo-user] Re: xorg segfaults if I have an encrypted volume mounted Remy Blank
2010-06-25 14:46 ` James L
2010-06-25 16:09 ` Remy Blank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i00nml$s68$1@dough.gmane.org' \
--to=remy.blank@pobox.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox