In the five days since I booted a 2.6.25-rc6 kernel on my development
machine, it has happened three times already that I came back to the
machine to find that the X server had exited, killing all applications
that still had a window open. This has never happened with previous
kernel versions (2.6.22.17, 2.6.24.3, 2.6.25-rc5), so I suspect some
relation to the latest rc kernel.
Syslog entries around the time of the crash (identical each time):
Mar 24 21:59:57 xenon kernel: [424469.161592] PM: Removing info for No
Bus:vcs7
Mar 24 21:59:57 xenon kernel: [424469.162591] PM: Removing info for No
Bus:vcsa7
Mar 24 21:59:57 xenon kernel: [424469.179556] uhci_hcd 0000:00:1d.1:
release dev 4 ep81-INT, period 8, phase 4, 93 us
Mar 24 21:59:57 xenon gconfd (ts-21705): Signal 15 erhalten,
ordungsgem??es Herunterfahren
Mar 24 21:59:57 xenon gconfd (ts-21705): Beenden
Mar 24 21:59:57 xenon gdm[21341]: WARNING: gdm_slave_xioerror_handler:
Schwerwiegender X-Fehler - :0 wird neu gestartet
Mar 24 21:59:58 xenon kernel: [426716.212842] PM: Adding info for No
Bus:vcs7
Mar 24 21:59:58 xenon kernel: [426716.213300] PM: Adding info for No
Bus:vcsa7
Mar 24 21:59:58 xenon kernel: [426716.295997] PM: Removing info for No
Bus:vcs7
Mar 24 21:59:58 xenon kernel: [426716.296110] PM: Removing info for No
Bus:vcsa7
Mar 24 21:59:59 xenon kernel: [426716.434662] PM: Adding info for No
Bus:vcs7
Mar 24 21:59:59 xenon kernel: [426716.434742] PM: Adding info for No
Bus:vcsa7
Mar 24 22:00:00 xenon kernel: [426717.727427] uhci_hcd 0000:00:1d.1:
reserve dev 4 ep81-INT, period 8, phase 4, 93 us
Mar 24 22:00:00 xenon kernel: [424472.319521] uhci_hcd 0000:00:1d.1:
release dev 4 ep81-INT, period 8, phase 4, 93 us
Mar 24 22:00:00 xenon kernel: [426717.997926] uhci_hcd 0000:00:1d.1:
reserve dev 4 ep81-INT, period 8, phase 4, 93 us
Mar 24 22:00:02 xenon gconfd (root-15531): (Version 2.20.0) wird
gestartet, Prozesskennung 15531, Benutzer ?root?
Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
?xml:readonly:/etc/gconf/gconf.xml.mandatory? wurde an der Position 0 zu
einer nur lesbaren Konfigurationsquelle aufgel?st
Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
?xml:readwrite:/root/.gconf? wurde an der Position 1 zu einer
schreibbaren Konfigurationsquelle aufgel?st
Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
?xml:readonly:/etc/gconf/gconf.xml.defaults? wurde an der Position 2 zu
einer nur lesbaren Konfigurationsquelle aufgel?st
Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
?xml:readonly:/etc/gconf/gconf.xml.schemas? wurde an der Position 3 zu
einer nur lesbaren Konfigurationsquelle aufgel?st
Mar 24 22:00:05 xenon kernel: [426722.904631] gtk-window-deco[15527]:
segfault at 4 ip b785c98a sp bfa4d160 error 4 in
libcairo.so.2.11.5[b7852000+7c000]
(The translation of the German error message from gdm is:
"Serious X error - restarting :0"
The German language messages from gconfd are probably not important,
as they appear identically during a regular X logout/login cycle.)
I'm at a loss where to start investigating this. Bisecting appears
impractical given the error happens about every other day with no
obvious triggering condition (except me being afk for a longer time.)
Configuration: Pentium D940, 2 GB RAM, Intel 965 chipset, Matrox
G550 PCIe graphics adapter, openSUSE 10.3 32 bit install.
Ideas?
Thanks
Tilman
On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
> In the five days since I booted a 2.6.25-rc6 kernel on my development
> machine, it has happened three times already that I came back to the
> machine to find that the X server had exited, killing all applications
> that still had a window open. This has never happened with previous
> kernel versions (2.6.22.17, 2.6.24.3, 2.6.25-rc5), so I suspect some
> relation to the latest rc kernel.
>
> Syslog entries around the time of the crash (identical each time):
>
> Mar 24 21:59:57 xenon kernel: [424469.161592] PM: Removing info for No
> Bus:vcs7
> Mar 24 21:59:57 xenon kernel: [424469.162591] PM: Removing info for No
> Bus:vcsa7
> Mar 24 21:59:57 xenon kernel: [424469.179556] uhci_hcd 0000:00:1d.1:
> release dev 4 ep81-INT, period 8, phase 4, 93 us
> Mar 24 21:59:57 xenon gconfd (ts-21705): Signal 15 erhalten,
> ordungsgem??es Herunterfahren
> Mar 24 21:59:57 xenon gconfd (ts-21705): Beenden
> Mar 24 21:59:57 xenon gdm[21341]: WARNING: gdm_slave_xioerror_handler:
> Schwerwiegender X-Fehler - :0 wird neu gestartet
> Mar 24 21:59:58 xenon kernel: [426716.212842] PM: Adding info for No
> Bus:vcs7
> Mar 24 21:59:58 xenon kernel: [426716.213300] PM: Adding info for No
> Bus:vcsa7
> Mar 24 21:59:58 xenon kernel: [426716.295997] PM: Removing info for No
> Bus:vcs7
> Mar 24 21:59:58 xenon kernel: [426716.296110] PM: Removing info for No
> Bus:vcsa7
> Mar 24 21:59:59 xenon kernel: [426716.434662] PM: Adding info for No
> Bus:vcs7
> Mar 24 21:59:59 xenon kernel: [426716.434742] PM: Adding info for No
> Bus:vcsa7
> Mar 24 22:00:00 xenon kernel: [426717.727427] uhci_hcd 0000:00:1d.1:
> reserve dev 4 ep81-INT, period 8, phase 4, 93 us
> Mar 24 22:00:00 xenon kernel: [424472.319521] uhci_hcd 0000:00:1d.1:
> release dev 4 ep81-INT, period 8, phase 4, 93 us
> Mar 24 22:00:00 xenon kernel: [426717.997926] uhci_hcd 0000:00:1d.1:
> reserve dev 4 ep81-INT, period 8, phase 4, 93 us
> Mar 24 22:00:02 xenon gconfd (root-15531): (Version 2.20.0) wird
> gestartet, Prozesskennung 15531, Benutzer ?root?
> Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
> ?xml:readonly:/etc/gconf/gconf.xml.mandatory? wurde an der Position 0 zu
> einer nur lesbaren Konfigurationsquelle aufgel?st
> Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
> ?xml:readwrite:/root/.gconf? wurde an der Position 1 zu einer
> schreibbaren Konfigurationsquelle aufgel?st
> Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
> ?xml:readonly:/etc/gconf/gconf.xml.defaults? wurde an der Position 2 zu
> einer nur lesbaren Konfigurationsquelle aufgel?st
> Mar 24 22:00:02 xenon gconfd (root-15531): Die Adresse
> ?xml:readonly:/etc/gconf/gconf.xml.schemas? wurde an der Position 3 zu
> einer nur lesbaren Konfigurationsquelle aufgel?st
> Mar 24 22:00:05 xenon kernel: [426722.904631] gtk-window-deco[15527]:
> segfault at 4 ip b785c98a sp bfa4d160 error 4 in
> libcairo.so.2.11.5[b7852000+7c000]
>
> (The translation of the German error message from gdm is:
> "Serious X error - restarting :0"
> The German language messages from gconfd are probably not important,
> as they appear identically during a regular X logout/login cycle.)
>
> I'm at a loss where to start investigating this. Bisecting appears
> impractical given the error happens about every other day with no
> obvious triggering condition (except me being afk for a longer time.)
>
> Configuration: Pentium D940, 2 GB RAM, Intel 965 chipset, Matrox
> G550 PCIe graphics adapter, openSUSE 10.3 32 bit install.
>
> Ideas?
anything in the X.org logfiles? does it happen with DRI off?
I don't think any of the DRM changes I made could cause this, so I'd
be looking towards something more generic..
Dave.
>
> Thanks
> Tilman
>
>
>
On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
> On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
>> In the five days since I booted a 2.6.25-rc6 kernel on my development
>> machine, it has happened three times already that I came back to the
>> machine to find that the X server had exited, killing all applications
>> that still had a window open. [...]
>
> anything in the X.org logfiles?
Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
| Backtrace:
| 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
| 1: [0xb7fc9400]
| 2:
/usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
[0xb51ea5dd]
| 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
| 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
| 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
| 6:
/usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
[0xb520cb83]
| 7:
/usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
[0xb51f8340]
| 8:
/usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
[0xb52471eb]
| 9:
/usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
[0xb52488e8]
| 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
[0xb5112663]
| 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
| 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
| 13: /usr/bin/X [0x815809e]
| 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
| 15: /usr/bin/X(main+0x47e) [0x807717e]
| 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
| 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
|
| Fatal server error:
| Caught signal 11. Server aborting
I have put the entire file at
http://gollum.phnxsoft.com/~ts/linux/Xorg.0.log.old
in case you want to have a look.
> does it happen with DRI off?
I guess it does, as my Xorg.0.log{,.old} says:
| (WW) MGA(0): Direct rendering disabled
HTH
Tilman
On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <[email protected]> wrote:
> On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
> > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
> >> In the five days since I booted a 2.6.25-rc6 kernel on my development
> >> machine, it has happened three times already that I came back to the
> >> machine to find that the X server had exited, killing all applications
> >> that still had a window open. [...]
>
> >
> > anything in the X.org logfiles?
>
> Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
>
> | Backtrace:
> | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
> | 1: [0xb7fc9400]
> | 2:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
> [0xb51ea5dd]
> | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
> | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
> | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
> | 6:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
> [0xb520cb83]
> | 7:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
> [0xb51f8340]
> | 8:
> /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
> [0xb52471eb]
> | 9:
> /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
> [0xb52488e8]
> | 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
> [0xb5112663]
> | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
> | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
> | 13: /usr/bin/X [0x815809e]
> | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
> | 15: /usr/bin/X(main+0x47e) [0x807717e]
> | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
> | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
> |
> | Fatal server error:
> | Caught signal 11. Server aborting
>
> I have put the entire file at
> http://gollum.phnxsoft.com/~ts/linux/Xorg.0.log.old
> in case you want to have a look.
>
>
> > does it happen with DRI off?
>
> I guess it does, as my Xorg.0.log{,.old} says:
>
> | (WW) MGA(0): Direct rendering disabled
>
> HTH
> Tilman
>
Looks like a GL screensaver kicks in and blows away your X server sw-GL..
not sure how a new kernel could cause this though..
memory layout changes maybe..
Dave.
>
On Tue 2008-03-25 10:53:38, Dave Airlie wrote:
> On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <[email protected]> wrote:
> > On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
> > > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
> > >> In the five days since I booted a 2.6.25-rc6 kernel on my development
> > >> machine, it has happened three times already that I came back to the
> > >> machine to find that the X server had exited, killing all applications
> > >> that still had a window open. [...]
> >
> > >
> > > anything in the X.org logfiles?
> >
> > Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
> >
> > | Backtrace:
> > | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
> > | 1: [0xb7fc9400]
> > | 2:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
> > [0xb51ea5dd]
> > | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
> > | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
> > | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
> > | 6:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
> > [0xb520cb83]
> > | 7:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
> > [0xb51f8340]
> > | 8:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
> > [0xb52471eb]
> > | 9:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
> > [0xb52488e8]
> > | 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
> > [0xb5112663]
> > | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
> > | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
> > | 13: /usr/bin/X [0x815809e]
> > | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
> > | 15: /usr/bin/X(main+0x47e) [0x807717e]
> > | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
> > | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
> > |
> > | Fatal server error:
> > | Caught signal 11. Server aborting
> >
> > I have put the entire file at
> > http://gollum.phnxsoft.com/~ts/linux/Xorg.0.log.old
> > in case you want to have a look.
> >
> >
> > > does it happen with DRI off?
> >
> > I guess it does, as my Xorg.0.log{,.old} says:
> >
> > | (WW) MGA(0): Direct rendering disabled
> >
> > HTH
> > Tilman
> >
>
> Looks like a GL screensaver kicks in and blows away your X server sw-GL..
>
> not sure how a new kernel could cause this though..
>
> memory layout changes maybe..
You can try to disable heap randomization...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Tue, Mar 25, 2008 at 10:53 AM, Dave Airlie <[email protected]> wrote:
>
> On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <[email protected]> wrote:
> > On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
> > > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
> > >> In the five days since I booted a 2.6.25-rc6 kernel on my development
> > >> machine, it has happened three times already that I came back to the
> > >> machine to find that the X server had exited, killing all applications
> > >> that still had a window open. [...]
> >
> > >
> > > anything in the X.org logfiles?
> >
> > Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
> >
> > | Backtrace:
> > | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
> > | 1: [0xb7fc9400]
> > | 2:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
> > [0xb51ea5dd]
> > | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
> > | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
> > | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
> > | 6:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
> > [0xb520cb83]
> > | 7:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
> > [0xb51f8340]
> > | 8:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
> > [0xb52471eb]
> > | 9:
> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
> > [0xb52488e8]
> > | 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
> > [0xb5112663]
> > | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
> > | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
> > | 13: /usr/bin/X [0x815809e]
> > | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
> > | 15: /usr/bin/X(main+0x47e) [0x807717e]
> > | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
> > | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
> > |
> > | Fatal server error:
> > | Caught signal 11. Server aborting
> >
any look finding what might have caused this?
it certainly looks like some heap or address space change affects Mesa.
Dave.
Dave Airlie wrote:
> On Tue, Mar 25, 2008 at 10:53 AM, Dave Airlie <[email protected]> wrote:
>> On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <[email protected]> wrote:
>> > On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
>> > > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <[email protected]> wrote:
>> > >> In the five days since I booted a 2.6.25-rc6 kernel on my development
>> > >> machine, it has happened three times already that I came back to the
>> > >> machine to find that the X server had exited, killing all applications
>> > >> that still had a window open. [...]
>> >
>> > >
>> > > anything in the X.org logfiles?
>> >
>> > Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
>> >
>> > | Backtrace:
>> > | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
>> > | 1: [0xb7fc9400]
>> > | 2:
>> > /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
>> > [0xb51ea5dd]
>> > | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
>> > | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
>> > | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
>> > | 6:
>> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
>> > [0xb520cb83]
>> > | 7:
>> > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
>> > [0xb51f8340]
>> > | 8:
>> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
>> > [0xb52471eb]
>> > | 9:
>> > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
>> > [0xb52488e8]
>> > | 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
>> > [0xb5112663]
>> > | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
>> > | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
>> > | 13: /usr/bin/X [0x815809e]
>> > | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
>> > | 15: /usr/bin/X(main+0x47e) [0x807717e]
>> > | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
>> > | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
>> > |
>> > | Fatal server error:
>> > | Caught signal 11. Server aborting
>> >
>
> any look finding what might have caused this?
>
> it certainly looks like some heap or address space change affects Mesa.
...
Mmm.. I've had one X-server death so far with 2.6.25-rc7.
Didn't keep the logfile, though.
-ml