Ubuntu
xorg-server package

Xorg crashed with SIGSEGV in _nv001647X()

Bug #473399 reported by Camilo Nova on 2009-11-03

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

Dont know

ProblemType: Crash
Architecture: i386
Date: Tue Nov 3 16:22:47 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 002: ID 0566:3002 Monterey International Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MSI MS-7309
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.6.4-2ubuntu4 [modified: usr/lib/xorg/modules/extensions/libglx.so]
ProcCmdLine: root=UUID=f1c5e583-bfd6-452f-b0f0-07483175c6ea ro quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-yV3uJs/database -nolisten tcp vt7
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SegvAnalysis:
Segfault happened at: 0xb5fbd6fb <_nv001647X+43>: mov (%edi),%esi
PC (0xb5fbd6fb) 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
StacktraceTop:
_nv001647X ()
_nv001548X ()
Title: Xorg crashed with SIGSEGV in _nv001647X()
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups:

dmi.bios.date: 09/05/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V9.2
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7309
dmi.board.vendor: MSI
dmi.board.version: 1.0
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.:bvrV9.2:bd09/05/2008:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7309
dmi.product.version: 1.0
dmi.sys.vendor: MSI
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-14-generic-pae

Tags:

Revision history for this message

Camilo Nova (camilo-nova) wrote on 2009-11-03:

BootDmesg.txt Edit (40.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.0 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (9.5 KiB, text/plain; charset="utf-8")
GdmLogOld.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.4 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (87.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (112.0 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (3.6 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (15.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (15.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.5 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 (56.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-13: 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.