Ubuntu
xorg-server package

X crashed

Bug #569907 reported by Thomas Schwinge on 2010-04-25

This bug report is a duplicate of: Bug #539772: [MASTER] Lucid 2.6.32-16 crashed to login screen - miCopyRegion. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	Confirmed	Undecided	Unassigned
	xserver-xorg-video-ati (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: xorg

X just crashed. I had this X session going fine for a bunch of hours already, with both suspend to disk and suspend to RAM earlier today, and now I opened <http://grasshopper.com/> in Firefox, and it (the whole X session) crashed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun Apr 25 22:25:49 2010
DkmsStatus:
vboxnetadp, 3.1.4, 2.6.32-21-generic, i686: installed
vboxdrv, 3.1.4, 2.6.32-21-generic, i686: installed
vboxnetflt, 3.1.4, 2.6.32-21-generic, i686: installed
MachineType: IBM 2373K9G
PccardctlIdent:
Socket 0:
   no product info available
Socket 1:
   no product info available
PccardctlStatus:
Socket 0:
   no card
Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=/dev/mapper/vg0-hostname--root ro crashkernel=384M-2G:64M,2G-:128M
SourcePackage: xorg
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2373K9G
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373K9G:pvrThinkPadT42:rvnIBM:rn2373K9G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2373K9G
dmi.product.version: ThinkPad T42
dmi.sys.vendor: IBM
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-21-generic

Tags:

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-25:

BootDmesg.txt Edit (45.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (124.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (33.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (42.9 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (33.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (644 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (777 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (529 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (311 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (103.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (225.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (37.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (47.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.4 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (15.0 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (1.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (267 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-25:

XorgLogOld.txt contains the crash's backtrace:

    Backtrace:
    0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]
    1: /usr/bin/X (0x8048000+0x61c7d) [0x80a9c7d]
    2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb8f410]
    3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xcbc000+0xb2039) [0xd6e039]
    4: /usr/lib/xorg/modules/libexa.so (0x8c0000+0x9490) [0x8c9490]
    5: /usr/lib/xorg/modules/libexa.so (0x8c0000+0x9558) [0x8c9558]
    6: /usr/bin/X (miCopyRegion+0x21b) [0x819cabb]
    7: /usr/bin/X (miDoCopy+0x44d) [0x819cfdd]
    8: /usr/lib/xorg/modules/libexa.so (0x8c0000+0x7a4a) [0x8c7a4a]
    9: /usr/bin/X (0x8048000+0xda9a3) [0x81229a3]
    10: /usr/bin/X (0x8048000+0x28df5) [0x8070df5]
    11: /usr/bin/X (0x8048000+0x2a477) [0x8072477]
    12: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a]
    13: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x2fabd6]
    14: /usr/bin/X (0x8048000+0x1e961) [0x8066961]
    Segmentation fault at address (nil)

Caught signal 11 (Segmentation fault). Server aborting

Perhaps a problem in the Radeon driver?

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-25:

``Of course'' it is not reproducable re-visiting <http://grasshopper.com/> now.

I see there are some X.org packages updates available. Will install them now. The system had the state as of 2010-04-23 10:01:13 (Ubuntu lucid).

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-26:

Crash #2 Edit (38.9 KiB, application/x-trash)

I just hit this two more times in a row, see the newly attached files. Again, this happened when visitian new pages in Firefox.

Can this be a bug in the Radeon driver?

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-26:

Crash #3 Edit (38.9 KiB, text/plain)

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-26:

I forgot: the system now is a totally up-to-date Ubuntu lucid one, and had an uptime of only 23 minutes when Crash #2 happened; Crash #3 followed only a few minutes later.

Bryce Harrington (bryce) on 2010-04-26

affects:

xorg (Ubuntu) → xorg-server (Ubuntu)

Bryce Harrington (bryce) on 2010-04-26

tags:	added: crash
Changed in xorg-server (Ubuntu):
status:	New → Confirmed
Changed in xserver-xorg-video-ati (Ubuntu):
status:	New → Confirmed

Revision history for this message

Thomas Schwinge (tschwinge) wrote on 2010-04-27:

Two further crashes today, always Firefox was ``involved''. Please tell me how you'd like me to help debugging this. Shall I rebuild the X server with debugging symbols? Shall I try some upstream sources? Etc.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #539772 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuxorg-server package

X crashed

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg-server package