Xorg crashed with SIGSEGV in FatalError() / OsInit() while trying to install linux-headers 2.6.31-9-rt

Bug #504497 reported by Gerhard Lang
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
High
Unassigned

Bug Description

headers are installed, then system asks for grub's dev, marking one, hit enter --> this alert

ProblemType: Crash
Architecture: i386
Date: Thu Jan 7 19:42:53 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100106)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.7.3.901-1ubuntu4 [modified: usr/lib/xorg/modules/extensions/libglx.so]
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-9-generic-pae root=/dev/sdb3
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-dGgCaD/database -nolisten tcp
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic-pae
RelatedPackageVersions:
 xserver-xorg 1:7.5~3ubuntu4
 libgl1-mesa-glx 7.6.1~rc3-1ubuntu1
 libdrm2 2.4.14-1ubuntu2
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0x249137 <strchrnul+23>: mov (%eax),%cl
 PC (0x00249137) ok
 source "(%eax)" (0x0000000b) not located in a known VMA region (needed readable region)!
 destination "%cl" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 FatalError ()
 LockServer ()
 OsInit ()
 _start ()
Tags: lucid
Title: Xorg crashed with SIGSEGV in FatalError()
Uname: Linux 2.6.32-9-generic-pae i686
UserGroups:

dmi.bios.date: 12/17/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: AM2NF3-VSTA
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd12/17/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF3-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
fglrx: Not loaded
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-9-generic-pae

Related branches

Revision history for this message
Gerhard Lang (lang-gerhard) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 LockServer ()
 OsInit ()
 _start ()
ThreadStacktrace:

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
visibility: private → public
Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV in FatalError() while trying to install linux-
- headers 2.6.31-9-rt
+ Xorg crashed with SIGSEGV in FatalError() / OsInit() while trying to
+ install linux-headers 2.6.31-9-rt
Revision history for this message
Bryce Harrington (bryce) wrote :

I believe this X crash is due to error messages being printed to the log file after the log file has been closed. This was being done in the signal handler due to a Ubuntu patch. I've corrected the patch to not print these errors, which should eliminate this crash.

However, still whatever problem had caused the X error to begin with is still there, and it is likely that X will still be failing, just without crashing (or perhaps with a different kind of crash). This crash is hiding that information however. So the good news is hopefully this will unhide that information. After updating to version 2:1.7.3.902-1ubuntu7 please re-test your original issue; if it still occurs file a new bug. Hopefully apport will provide better information in this case now.

Changed in xorg-server (Ubuntu):
importance: Medium → High
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.7.3.902-1ubuntu7

---------------
xorg-server (2:1.7.3.902-1ubuntu7) lucid; urgency=low

  * Update 100_rethrow_signals.patch: Don't log more error messages after
    the log has been closed, else it causes a SIGSEGV (signal 11) crash
    under several different conditions, including on even ordinary error
    exits.
    (LP: #506510, #507345, #506977, #504497, #507083)
 -- Bryce Harrington <email address hidden> Fri, 15 Jan 2010 15:22:34 -0800

Changed in xorg-server (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.