Xorg crash in miValidateTree()

[Pete Keller]

Server aborts randomly, can run for 3 or 4 days without aborting, however, it has also aborted 5 minutes after previous abort.

xorg package version 1:7.4~5ubuntu3
xserver-xorg-core package vrsion2:1.5.2-2ubuntu3

appears to be similar to bug 303807.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: xorg 1:7.4~5ubuntu3
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.20-15-generic (User Name@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007

SourcePackage: xorg
Uname: Linux 2.6.20-15-generic i686
xkbcomp:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/lib/libpixman-1.so.0(pixman_region_intersect+0x234) [0xb7e3f6d4]
4: /usr/X11R6/bin/X(miIntersect+0x2b) [0x811d59b]
5: /usr/X11R6/bin/X [0x8120e46]
6: /usr/X11R6/bin/X [0x8120e61]
7: /usr/X11R6/bin/X(miValidateTree+0x1ba) [0x81215ca]
8: /usr/lib/xorg/modules/extensions//libdri.so(DRIValidateTree+0x61) [0xb7ee5d51]
9: /usr/X11R6/bin/X(miMoveWindow+0x271) [0x8127d71]
10: /usr/X11R6/bin/X(compMoveWindow+0xb3) [0x8142ae3]
11: /usr/X11R6/bin/X(ConfigureWindow+0x5ca) [0x807848a]
12: /usr/X11R6/bin/X(ProcConfigureWindow+0x92) [0x808be42]
13: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
14: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
15: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0e685]
16: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: ASUSTeK Computer Inc. Device [1043:1297]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: ASUSTeK Computer Inc. Device [1043:1252]

[Dan Trevino (dantrevino)]

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.

[Bryce Harrington (bryce)]

Please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

[Pete Keller (pete-keller)]

Bryce,

I will try to get to the backtrace this weekend, both my wife and I are sick however.

--- On Thu, 3/19/09, Bryce Harrington <email address hidden> wrote:

> From: Bryce Harrington <email address hidden>
> Subject: [Bug 334944] Re: [Intrepid] Xorg "Saw signal 11. Server aborting."
> To: <email address hidden>
> Date: Thursday, March 19, 2009, 9:41 PM
> Please collect a full backtrace - see
> http://wiki.ubuntu.com/X/Backtracing for directions.
>
> ** Description changed:
>
> Server aborts randomly, can run for 3 or 4 days without
> aborting,
> however, it has also aborted 5 minutes after previous
> abort.
>
> xorg package version 1:7.4~5ubuntu3
> xserver-xorg-core package vrsion2:1.5.2-2ubuntu3
>
> appears to be similar to bug 303807.
>
> ProblemType: Bug
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> Package: xorg 1:7.4~5ubuntu3
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersion: Linux version 2.6.20-15-generic (User
> Name@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2
> SMP Sun Apr 15 07:36:31 UTC 2007
>
> SourcePackage: xorg
> Uname: Linux 2.6.20-15-generic i686
> xkbcomp:
> +
> +
> + Backtrace:
> + 0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
> + 1: [0xffffe420]
> + 2: [0xffffe420]
> + 3:
> /usr/lib/libpixman-1.so.0(pixman_region_intersect+0x234)
> [0xb7e3f6d4]
> + 4: /usr/X11R6/bin/X(miIntersect+0x2b) [0x811d59b]
> + 5: /usr/X11R6/bin/X [0x8120e46]
> + 6: /usr/X11R6/bin/X [0x8120e61]
> + 7: /usr/X11R6/bin/X(miValidateTree+0x1ba) [0x81215ca]
> + 8:
> /usr/lib/xorg/modules/extensions//libdri.so(DRIValidateTree+0x61)
> [0xb7ee5d51]
> + 9: /usr/X11R6/bin/X(miMoveWindow+0x271) [0x8127d71]
> + 10: /usr/X11R6/bin/X(compMoveWindow+0xb3) [0x8142ae3]
> + 11: /usr/X11R6/bin/X(ConfigureWindow+0x5ca) [0x807848a]
> + 12: /usr/X11R6/bin/X(ProcConfigureWindow+0x92)
> [0x808be42]
> + 13: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
> + 14: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
> + 15: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)
> [0xb7b0e685]
> + 16: /usr/X11R6/bin/X [0x8071101]
> + Saw signal 11. Server aborting.
>
> ** Changed in: xorg-server (Ubuntu)
> Importance: Undecided => High
> Status: Confirmed => Incomplete
>
> --
> [Intrepid] Xorg "Saw signal 11. Server aborting."
> https://bugs.launchpad.net/bugs/334944
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “xorg-server” source package in Ubuntu:
> Incomplete
>
> Bug description:
> Server aborts randomly, can run for 3 or 4 days without
> aborting, however, it has also aborted 5 minutes after
> previous abort.
>
> xorg package version 1:7.4~5ubuntu3
> xserver-xorg-core package vrsion2:1.5.2-2ubuntu3
>
> appears to be similar to bug 303807.
>
> ProblemType: Bug
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> Package: xorg 1:7.4~5ubuntu3
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersion: Linux version 2.6.20-15-generic ...

[Bryce Harrington (bryce)]

Hope your wife and you have recovered, let us know when you get the backtrace.

[Christian van den Bosch (cjb)]

Hi,

I'm getting what I think is precisely the same problem, twice since upgrading from Hardy to Intrepid yesterday. Both times JOSM was the foreground app; this a Java app for editing OpenStreetMap. I've never had this problem on Hardy.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/X11R6/bin/X(WriteEventsToClient+0x1ca) [0x80959ca]
4: /usr/X11R6/bin/X(TryClientEvents+0xe8) [0x8095ac8]
5: /usr/X11R6/bin/X(DeliverEventsToWindow+0x296) [0x8096436]
6: /usr/X11R6/bin/X(DeliverDeviceEvents+0x18b) [0x8096b8b]
7: /usr/X11R6/bin/X(DeliverGrabbedEvent+0x37f) [0x8097adf]
8: /usr/X11R6/bin/X(CoreProcessPointerEvent+0x35c) [0x809a12c]
9: /usr/X11R6/bin/X(ProcessPointerEvent+0xae) [0x819c55e]
10: /usr/X11R6/bin/X(mieqProcessInputEvents+0x172) [0x8110282]
11: /usr/X11R6/bin/X(ProcessInputEvents+0x2c) [0x80c39bc]
12: /usr/X11R6/bin/X(Dispatch+0x282) [0x808c7d2]
13: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
14: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf7685]
15: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"

Hardware: Fujitsu P2110

root@fuj:~ # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineTMx86
cpu family : 6
model : 4
model name : Transmeta(tm) Crusoe(tm) Processor TM5800
stepping : 3
cpu MHz : 859.348
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr cx8 sep cmov mmx longrun lrti
bogomips : 1734.51

root@fuj:~ # lspci
00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 02)
00:00.1 RAM memory: Transmeta Corporation SDRAM controller
00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)
00:06.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
00:0c.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
00:14.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64)

I have started Apport, but I may need some guidance on how to retrieve its log after a crash, as I run fluxbox rather than kde or gnome. I am cjb_ie on freenode.

Cheers,

Christian

[Christian van den Bosch (cjb)]

Actually, I wonder if this is an unrelated bug with a similar symptom. I would welcome an opinion as to whether I should file this as a separate bug.

Kind regards,

Christian

[Christian van den Bosch (cjb)]

apport-cli claims "No pending crash reports." after the latest crash :(

New backtrace:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/X11R6/bin/X(miRegionCopy+0x24) [0x811d5d4]
4: /usr/X11R6/bin/X(miSlideAndSizeWindow+0xb0d) [0x812891d]
5: /usr/X11R6/bin/X(compResizeWindow+0xb8) [0x81429c8]
6: /usr/X11R6/bin/X(ConfigureWindow+0xb23) [0x80789e3]
7: /usr/X11R6/bin/X(ProcConfigureWindow+0x92) [0x808be42]
8: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
9: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf7685]
11: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"

Frontmost app this time was gnome-terminal.

[Christian van den Bosch (cjb)]

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/X11R6/bin/X(WriteEventsToClient+0x1ca) [0x80959ca]
4: /usr/X11R6/bin/X(TryClientEvents+0xe8) [0x8095ac8]
5: /usr/X11R6/bin/X(DeliverEventsToWindow+0x296) [0x8096436]
6: /usr/X11R6/bin/X(DeliverDeviceEvents+0x18b) [0x8096b8b]
7: /usr/X11R6/bin/X(CoreProcessPointerEvent+0x2c6) [0x809a096]
8: /usr/X11R6/bin/X(ProcessPointerEvent+0xae) [0x819c55e]
9: /usr/X11R6/bin/X(mieqProcessInputEvents+0x172) [0x8110282]
10: /usr/X11R6/bin/X(ProcessInputEvents+0x2c) [0x80c39bc]
11: /usr/X11R6/bin/X(Dispatch+0x282) [0x808c7d2]
12: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
13: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf7685]
14: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"

Frontmost app was JOSM again. I'm getting the impression that in JOSM, the problem is most likely to occur when selecting or modifying a long way (connected series of nodes) - could it be a video driver issue related to drawing a connected series of lines?

[Christian van den Bosch (cjb)]

Still nothing from apport, but on trying

force_start=1 /etc/init.d/apport start

instead of

force_start=1 /etc/init.d/apport restart (as suggested by https://wiki.ubuntu.com/X/Backtracing) I'm informed that it's starting, so fingers crossed for the next time...

[Christian van den Bosch (cjb)]

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/X11R6/bin/X(WriteEventsToClient+0x1ca) [0x80959ca]
4: /usr/X11R6/bin/X(TryClientEvents+0xe8) [0x8095ac8]
5: /usr/X11R6/bin/X(DeliverEventsToWindow+0x296) [0x8096436]
6: /usr/X11R6/bin/X(DeliverDeviceEvents+0x18b) [0x8096b8b]
7: /usr/X11R6/bin/X(CoreProcessPointerEvent+0x2c6) [0x809a096]
8: /usr/X11R6/bin/X(ProcessPointerEvent+0xae) [0x819c55e]
9: /usr/X11R6/bin/X(mieqProcessInputEvents+0x172) [0x8110282]
10: /usr/X11R6/bin/X(ProcessInputEvents+0x2c) [0x80c39bc]
11: /usr/X11R6/bin/X(Dispatch+0x282) [0x808c7d2]
12: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
13: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf7685]
14: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"

Circumstances precisely the same as the previous crash (adding and moving a node to a long way in JOSM).

[Christian van den Bosch (cjb)]

Still no joy with apport, but I'm following https://wiki.ubuntu.com/DebuggingProgramCrash now for the next time.

[Christian van den Bosch (cjb)]

Here's a backtrace from gdb.

[Christian van den Bosch (cjb)]

Another five backtraces from gdb, all triggered by adding and moving a node in JOSM.

[Tobias Lietke (tobias-lietke)]

My Xserver also crashes since upgrading to 8.10. Maybe it is related, though it's a different call stack.
Often crashes when displaying context menus.

*** Workaround:
I'm using compiz & emerald now. Crash hasn't occurred anymore.
Maybe others can use it as well to have a working system until the problem is resolved.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x79) [0x80c3019]
1: [0xb7f5b420]
2: /usr/bin/X(UnmapWindow+0x1f8) [0x8076e28]
3: /usr/bin/X(compFreeClientWindow+0x23a) [0x8143b3a]
4: /usr/bin/X [0x8141164]
5: /usr/bin/X(FreeResource+0x10c) [0x807461c]
6: /usr/bin/X(compUnredirectWindow+0x7b) [0x81436db]
7: /usr/bin/X [0x8141abe]
8: /usr/bin/X [0x81290e5]
9: /usr/bin/X [0x8128ffc]
10: /usr/bin/X [0x8128ffc]
11: /usr/bin/X(miChangeSaveUnder+0x6b) [0x812919b]
12: /usr/bin/X(MapWindow+0x448) [0x8077658]
13: /usr/bin/X(ProcMapWindow+0x69) [0x808c019]
14: /usr/bin/X(Dispatch+0x34f) [0x808c89f]
15: /usr/bin/X(main+0x47d) [0x8071d1d]
16: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0x4746a685]
17: /usr/bin/X [0x8071101]
Saw signal 11. Server aborting.

[Pete Keller (pete-keller)]

Bryce,

Thanks, my wife and I are both feeling better... not good, just better. 8)

Lack of back trace attached.

Key lines shown below:

(gdb) attach 6821
Attaching to program: /usr/bin/Xorg, process 6821
/build/buildd/gdb-6.8/gdb/linux-nat.c:988: internal-error: linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) && WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

[Christian van den Bosch (cjb)]

Pete,

I've worked around this problem (so far anyway) by pinning my Xorg back to the hardy version, following the apt-pinning howto at:
  http://www.howtoforge.com/a-short-introduction-to-apt-pinning

The -t argument to apt-get didn't seem to work quite as described, so I ended up with a very verbose /etc/apt/preferences which I've uploaded at
  http://cjb.ie/apt-preferences.txt

I then proceeded with
  apt-get update
  apt-get install xserver-xorg

and discovered one dependency problem, where apt complained that xserver-xorg-driver-video-ati and xserver-xorg-driver-video-radeon had a conflict concerning a manpage, even though it was going to remove the latter package. I resolved this with:
  dpkg --force-all -r xserver-xorg-driver-video-radeon
  apt-get -f install

I hope this helps you!

Christian

[Bryce Harrington (bryce)]

Christian and Tobias, neither of you have the same backtrace as Pete, as neither of your crashes reference miValidateTree at all, so I'm unsure why you're posting to pete's bug? If you're just trying to shanghai his bug, don't do that, we're just going to focus on his backtrace bug, so if you want your issues investigated you're going to have to file them as separate bug reports.

[Christian van den Bosch (cjb)]

Hi Bryce,

I'm mailing you directly to reduce noise on launchpad - apologies if
this is inappropriate.

Apologies for misfiling, but as I did write two weeks ago (
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/334944/comments/7
) I was unsure whether this was a related bug or not, and sought
guidance as to where to file it. Please don't accuse me of sabotage.

Given that there is so little consistency between the backtraces I
posted, the last half dozen of which were all triggered the same way, it
smells of some asynchronous behavour. Should I file multiple separate
bugs? One bug? Some of my backtraces reference other mi* functions, some
don't.

Thank you for your assistance on this.

Kind regards,

Christian van den Bosch

Bryce Harrington wrote:
> Christian and Tobias, neither of you have the same backtrace as Pete, as
> neither of your crashes reference miValidateTree at all, so I'm unsure
> why you're posting to pete's bug? If you're just trying to shanghai his
> bug, don't do that, we're just going to focus on his backtrace bug, so
> if you want your issues investigated you're going to have to file them
> as separate bug reports.
>
> ** Changed in: xorg-server (Ubuntu)
> Status: Confirmed => Triaged
>

--
Christian / cjb

http://www.cjb.ie/

[Tobias Lietke (tobias-lietke)]

Bryce Harrington wrote:
Christian and Tobias, neither of you have the same backtrace as Pete, as
neither of your crashes reference miValidateTree at all, so I'm unsure
why you're posting to pete's bug?

Just wanted to post my workaround for others to try.
Sorry for any inconvenience.
Regards,
Tobias

[Pete Keller (pete-keller)]

I have upgraded to jaunty.

When I upgraded, the problems went away. I have had long uptimes on the server.

This bug can be closed

Thanks
Pete