Xorg crash after resuming from suspend in lucid lynx

[audacity3537]

Suspending and resuming works okay. But after about 10 minutes of usage after suspending, it will crash and the cli screen will flicker till I reset the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue Jun 1 12:20:41 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard Presario V2000 (PY897PA#UUF)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=b020d83e-1a07-4c33-a596-fcb073889743 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_SG.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
dmi.bios.date: 03/23/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.name: 308F
dmi.board.vendor: Quanta
dmi.board.version: 46.13
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd03/23/2006:svnHewlett-Packard:pnPresarioV2000(PY897PA#UUF):pvrRev1:rvnQuanta:rn308F:rvr46.13:cvnQuanta:ct10:cvrN/A:
dmi.product.name: Presario V2000 (PY897PA#UUF)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in xorg-server.
(With many applications, you can report a future bug directly on the appropriate package by opening the application's "Help" menu and choosing "Report a Problem". https://wiki.ubuntu.com/ReportingBugs)

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Here you can find the specific instructions for a XServer Crash on Resume: https://wiki.ubuntu.com/X/Troubleshooting/XServerCrashOnResume

[audacity3537 (audacity3537)]

Hope this helps.

[audacity3537 (audacity3537)]

Sorry, I made a mistake. Kindly please ignore the previous gdb-Xorg.txt file.

[Leo Arias (elopio)]

Hello,

The trace attached is not useful, because it is missing debugging symbols. Did you installed the packages as explained here

https://wiki.ubuntu.com/X/Backtracing#Debug%20symbol%20information

?

[audacity3537 (audacity3537)]

I've installed the debugging packages as stated in the instructions, but I keep getting messages like this:

Reading symbols from /usr/bin/Xorg...warning: the debug information found in "/usr/lib/debug//usr/bin/Xorg" does not match "/usr/bin/Xorg" (CRC mismatch).

Attached is the full gdb output. Apport doesn't seem to catch the crash. Pls advise. Thx.

[audacity3537 (audacity3537)]

Attached is the list of dbg packages I've installed. Am I missing other packages?

[audacity3537 (audacity3537)]

Ok, I've done a fresh install of Lucid Lynx on my laptop, enabled the lucid-proposed respository, and installed:

xorg 1:7.5+5ubuntu1 ;
xserver-xorg-core 2:1.7.6-2ubuntu7.1 ; and
xserver-xorg-core-dbg 2:1.7.6-2ubuntu7.1.

That seem to solve the 'CRC mismatch' errors, and the traceback of Xorg seems more promising this time. Hope this is more useful.

[Leo Arias (elopio)]

NgCH,

Thanks for following up this problem, but the backtrace is still incomplete.

After reproducing the problem using the debugger, please enter this command in the gdb console:
'thread apply all bt full'

and then attach the output file to this report.

thanks again.
pura vida.

[audacity3537 (audacity3537)]

Okay, I hope this one has been done correctly.

Just a helpful note: This backtrace was taken after resuming from suspend and entering my password at the login dialog box. The 'program exited' happened when Xorg crash after a few minutes of usage.

[Leo Arias (elopio)]

NgCH, thanks, but we need you to start the debugging before suspending the machine, and to execute the command:

thread apply all bt full

on the debugger just after the xorg crash.

[audacity3537 (audacity3537)]

Hi Leo.

Many thanks for your patience. I've tried doing the backtrace again, this time starting X without gdm (https://wiki.ubuntu.com/DebuggingXorg#Debugging Error Exits). But when Xorg crashed after resuming from suspend, the command "thread apply all bt full" doesn't give me anything:

(gdb) cont
Continuing.

Program exited with code 01.
(gdb) thread apply all bt full
(gdb) detach
The program is not being run.

The attached file is the full output of gdb, which was already running before I suspended the laptop.

Sorry for the blunders. I'm quite new to this and I'm still not sure if I've done it correctly. :-S

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]