Bug#533509: xorg: Random crash

[Marco <marco.berto@gmail.com>]

Il giorno gio, 18/06/2009 alle 12.07 +0200, Julien Cristau ha scritto:
> severity 533509 important
> reassign 533509 xserver-xorg-video-intel 2:2.3.2-2+lenny6
> kthxbye
>
> On Thu, Jun 18, 2009 at 10:38:18 +0200, Marco B wrote:
>
> > The XServer crashes random once or twice in a (working) day, without a particular reason.
> > I see a black screen and i can't access to terminal.
> > I use the latest GNOME, no compiz.
> > 
> > Here the logs.
> > 
> That log doesn't show a crash.  Do you have one that does?  Also please
> try upgrading X, and possibly your kernel, to the version in unstable,
> see if the crashes still happen.

Here's some part of a syslog:

[..cut..]

Jun 18 13:12:26 tecra -- MARK --
Jun 18 13:17:01 tecra /USR/SBIN/CRON[25099]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 18 13:32:26 tecra -- MARK --
Jun 18 13:52:26 tecra -- MARK --
Jun 18 13:56:36 tecra acpid: client 3064[0:0] has disconnected 
Jun 18 13:56:37 tecra gdm[3055]: WARNING: gdm_slave_xioerror_handler: errore fatale di X. Riavvio di :0 in corso 
Jun 18 13:56:43 tecra console-kit-daemon[2884]: WARNING: Unable to activate console: No such device or address 
Jun 18 13:56:43 tecra acpid: client connected from 28600[0:0] 
Jun 18 13:56:43 tecra acpid: 1 client rule loaded 
Jun 18 13:56:44 tecra bonobo-activation-server (merk-28613): could not associate with desktop session: Failed to connect to socket /tmp/dbus-ymElCQqEKx: Connessione rifiutata
Jun 18 13:56:57 tecra acpid: client 28600[0:0] has disconnected 
Jun 18 13:56:57 tecra acpid: client connected from 28646[0:0] 
Jun 18 13:56:57 tecra acpid: 1 client rule loaded 
Jun 18 13:57:11 tecra acpid: client 28646[0:0] has disconnected 
Jun 18 13:57:11 tecra acpid: client connected from 28670[0:0] 
Jun 18 13:57:11 tecra acpid: 1 client rule loaded 
Jun 18 13:57:23 tecra acpid: client 28670[0:0] has disconnected 
Jun 18 13:57:39 tecra gdm[3049]: WARNING: Fallito l'avvio del server X troppe volte in poco tempo, display :0 disattivato 
Jun 18 13:58:00 tecra acpid: client connected from 29016[0:0] 
Jun 18 13:58:00 tecra acpid: 1 client rule loaded 
Jun 18 13:58:26 tecra acpid: client 29016[0:0] has disconnected 
Jun 18 13:58:32 tecra shutdown[29258]: shutting down for system reboot
Jun 18 13:58:32 tecra init: Switching to runlevel: 6
Jun 18 13:58:33 tecra console-kit-daemon[2884]: WARNING: Unable to activate console: No such device or address 
Jun 18 13:58:34 tecra rpc.statd[2318]: Caught signal 15, un-registering and exiting.
Jun 18 13:58:36 tecra kernel: [13717.044297] fuse exit
Jun 18 13:58:38 tecra kernel: [13718.837052] Bluetooth: Core ver 2.11
Jun 18 13:58:38 tecra kernel: [13718.838167] NET: Registered protocol family 31
Jun 18 13:58:38 tecra kernel: [13718.838167] Bluetooth: HCI device and connection manager initialized
Jun 18 13:58:38 tecra kernel: [13718.838167] Bluetooth: HCI socket layer initialized
Jun 18 13:58:38 tecra kernel: [13718.879718] Bluetooth: L2CAP ver 2.9
Jun 18 13:58:38 tecra kernel: [13718.879718] Bluetooth: L2CAP socket layer initialized
Jun 18 13:58:38 tecra kernel: [13718.916802] Bluetooth: RFCOMM socket layer initialized
Jun 18 13:58:38 tecra kernel: [13718.916802] Bluetooth: RFCOMM TTY layer initialized
Jun 18 13:58:38 tecra kernel: [13718.916802] Bluetooth: RFCOMM ver 1.8
Jun 18 13:58:38 tecra avahi-daemon[2672]: Got SIGTERM, quitting.
Jun 18 13:58:38 tecra avahi-daemon[2672]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::218:deff:fe18:e387.
Jun 18 13:58:38 tecra avahi-daemon[2672]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.85.52.
Jun 18 13:58:38 tecra kernel: Kernel logging (proc) stopped.
Jun 18 13:58:38 tecra kernel: Kernel log daemon terminating.
Jun 18 13:58:39 tecra exiting on signal 15
Jun 18 14:00:18 tecra syslogd 1.5.0#5: restart.

[..cut..]

You need other logs?



> Cheers,
> Julien

Thanks, Marco.