Xorg crashed with SIGSEGV

[KeenEars]

I`m experiencing frequent (1-2 per day) and random Xorg crashes.Using Kubuntu 9.10. Usually this seems to be happen when some GUI action is taking place (like showing the Kopete messages coming up) and the Xorg suddenly dies. As I can understand with the trace information, this happens on nvidia drivers, which was patched recently to use newer libc patch. Before the libc update, I can`t say if this happened this often. I have some more crash info collected and will attach it a bit later. Thanks!

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Sep 28 11:17:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.6.3-1ubuntu7
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=ce41421d-9558-4b96-bf10-573e0e256c26 ro quiet splash
ProcCmdline: /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-6vXfa2
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu6
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
SegvAnalysis:
 Segfault happened at: 0x30315fb: mov (%edi),%esi
 PC (0x030315fb) 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 0x030315fb in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 1506):
 #0 0x030315fb in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
Title: Xorg crashed with SIGSEGV
Uname: Linux 2.6.31-11-generic i686
UserGroups:

dmi.bios.date: 07/06/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.name: P5WD2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd07/06/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-11-generic

[lspci]
03:00.0 VGA compatible controller [0300]: nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] [10de:0161] (rev a1)

[KeenEars (fl-blade)]

As of today, crashes comes constantly and suddenly. I`ll try to send some info about it, but this can happen any second now.
I`ve compressed the older log because the crash ifo was too heavy(includes core dump)

[KeenEars (fl-blade)]

<<AttachList>>

[Apport retracing service (apport)]

StacktraceTop:?? ()

[KeenEars (fl-blade)]

Sorry, I can`t figure out how to post multiple files here, so I post some more today`s zipped logs

[KeenEars (fl-blade)]

I`ve temporarily switched to nv, because I was unable to work in such unstable situation. Should I recheck if something is changed ? Newest libc update failed to install on my sustem today though. (filed a duplicate of bug #441090 )

[KeenEars (fl-blade)]

Again the crash (look at #450098). Will see if these crashes will return after all the latest fixes.

[KeenEars (fl-blade)]

Currently I`m on nvidia-173 and no crashes yet

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[KeenEars (fl-blade)]

Well, you can delete this one (i`m still on 9.10 and it sometimes crash), because noone will fix it. None of my bugs was.
You need the one more tag for all these bugs: "We`ve got something better to do"

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.