[lucid] X server crash

[Wenzhuo Zhang]

Binary package hint: xserver-xorg

After upgrading my ThinkPad X32 to Ubuntu 10.04 beta, I often experience X server crash when typing in the search bar of Firefox.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e880b]
1: /usr/bin/X (0x8048000+0x61aed) [0x80a9aed]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0x4f6410]
3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x2b3000+0xb20f9) [0x3650f9]
4: /usr/lib/xorg/modules/libexa.so (0x1e9000+0x9490) [0x1f2490]
5: /usr/lib/xorg/modules/libexa.so (0x1e9000+0x9558) [0x1f2558]
6: /usr/bin/X (miCopyRegion+0x21b) [0x819ac9b]
7: /usr/bin/X (miDoCopy+0x44d) [0x819b1bd]
8: /usr/lib/xorg/modules/libexa.so (0x1e9000+0x7a1a) [0x1f0a1a]
9: /usr/bin/X (0x8048000+0xd9e83) [0x8121e83]
10: /usr/bin/X (0x8048000+0x28dd5) [0x8070dd5]
11: /usr/bin/X (0x8048000+0x2a457) [0x8072457]
12: /usr/bin/X (0x8048000+0x1ed3a) [0x8066d3a]
13: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x5afbd6]
14: /usr/bin/X (0x8048000+0x1e921) [0x8066921]
Segmentation fault at address (nil)

Caught signal 11 (Segmentation fault). Server aborting

[Wenzhuo Zhang (wenzhuo)]

Attaching xorg.conf. (X server crashes too when using XAA.)

[Bryce Harrington (bryce)]

Hi Wenzhuo,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

Please attach the output of `lspci -vvnn` too.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

Are you able to reproduce this issue easily? If so, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions. If not, could you describe the conditions under which the crash tends to occur?

[Wenzhuo Zhang (wenzhuo)]

On 03/30/2010 05:05 PM, Bryce Harrington wrote:
> Are you able to reproduce this issue easily?

Yes, every time.

> If so, please collect a
> full backtrace - see http://wiki.ubuntu.com/X/Backtracing for
>

The backtrace collected by gdb contains much less information
than what X collected.

> directions. If not, could you describe the conditions under which the
> crash tends to occur?
>

Just start firefox, and type slowly in the address bar as the
incremental search drop down menu of the search history
appears. For example, I have a lot of keywords starting with x or
xorg in the search history. I just have to type "x serv...", and X
crashes at the fifth or sixth character. It's reproducible every time.

[Wenzhuo Zhang (wenzhuo)]

Sorry, I mean the search bar. It seems that typing in the address bar cannot reproduce the crash.