All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: [2.6.25-rc6] possible regression: X server dying
Date: Mon, 24 Mar 2008 23:38:32 +0100	[thread overview]
Message-ID: <47E82D68.5070305@imap.cc> (raw)

[-- Attachment #1: Type: text/plain, Size: 3434 bytes --]

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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

             reply	other threads:[~2008-03-24 22:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 22:38 Tilman Schmidt [this message]
2008-03-24 23:22 ` [2.6.25-rc6] possible regression: X server dying Dave Airlie
2008-03-24 23:45   ` Tilman Schmidt
2008-03-25  0:53     ` Dave Airlie
2008-03-26 18:52       ` Pavel Machek
2008-03-31  4:53       ` Dave Airlie
2008-03-31 17:45         ` Mark Lord
2008-04-01  9:02         ` Tilman Schmidt
2008-04-06  7:44           ` Dave Airlie
2008-04-06 14:34             ` Gerhard Pircher
2008-04-07 22:27               ` Dave Airlie
2008-04-08 21:01                 ` Guennadi Liakhovetski
2008-04-09  8:54                   ` Gerhard Pircher
2008-04-24 16:40                     ` Oliver Pinter
2008-04-24 20:37                       ` Gerhard Pircher
2008-04-24 16:03                   ` Guennadi Liakhovetski
2008-04-19 11:30             ` [2.6.25] X server dying due to lock not being held Gerhard Pircher
2008-04-07 22:22           ` [2.6.25-rc6] possible regression: X server dying Tilman Schmidt
2008-04-07 22:55             ` Ray Lee
2008-04-09 11:57               ` Tilman Schmidt
2008-04-14  1:02               ` Tilman Schmidt
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` [2.6.25-rc6] possible regression: X server dying Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47E82D68.5070305@imap.cc \
    --to=tilman@imap.cc \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.