Ubuntu
xorg-server package

Xorg crashed with SIGSEGV in _nv001647X()

Bug #425120 reported by E.T. Anderson on 2009-09-06

This bug report is a duplicate of: Bug #443259: Xorg crashed with SIGSEGV in _nv001647X(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	New	Undecided	Unassigned

Bug Description

X crashed on Korganizer maximize.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 6 01:58:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MXC062
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.6.3-1ubuntu5
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-9-generic root=UUID=072b150f-9072-4b2d-ae6c-a1ca8dc5a663 ro quiet splash
ProcCmdline: /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-ce7n45
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
libdrm2 2.4.12+git20090801.45078630-0ubuntu1
xserver-xorg-video-intel 2:2.8.1-1ubuntu1
xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
SegvAnalysis:
Segfault happened at: 0x34885fb <_nv001647X+43>: mov (%edi),%esi
PC (0x034885fb) ok
source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
Stacktrace:
#0 0x034885fb in _nv001647X ()
from /usr/lib/xorg/modules/drivers//nvidia_drv.so
#1 0x03490790 in _nv001548X ()
from /usr/lib/xorg/modules/drivers//nvidia_drv.so
StacktraceTop:
_nv001647X ()
_nv001548X ()
Title: Xorg crashed with SIGSEGV in _nv001647X()
Uname: Linux 2.6.31-9-generic i686
UserGroups:

dmi.bios.date: 04/02/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0FP985
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/02/2007:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn0FP985:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MXC062
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-9-generic

Tags:

Revision history for this message

E.T. Anderson (firebringer11) wrote on 2009-09-06:

BootDmesg.txt Edit (44.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (23.2 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (83.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (181.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (13.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (14.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.1 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (26.1 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (30.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-06: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #419399, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.