Re: Computer Freezes - how to find out what happened?
Question, when freezes happen, were you away from the keyboard and mouse
for a while? If so, the screen-saver program needs the delay time
increased so it takes longer to turn on. I don't know how to exit
screen-saver mode and bring a computer back to life in X yet. If orca
is used it's recommended to disable the screen-saver entirely.
On Wed, 20 Jul 2011, Alan Chandler wrote:
> I have just built myself a new computer (i5 2500 with Intel Motherboard) and
> am getting a situation where the user interface freezes every so often.
>
> I suspect it is more than just X freezing, because when that has happened in
> the past I can ssh into the machine console and still do things. In this new
> circumstance I can't.
>
> However I suspect its not a completely solid freeze of the hardware, because
> if I push the reset button on the computer, after a delay of maybe 15 or 20
> seconds the screen goes blank and then it successfully reboots itself. During
> that reboot sequence there is no indication that the previous shutdown was not
> successful. I.E what appears to be the case is that the reset kicks init into
> a successful shutdown and reboot.
>
> The only indication I can find in the log of anything strange is the Init "co"
> respawning too fast messages.
>
> Here is syslog over the period of the reboot (apologies for mail wordwrap).
>
> Jul 20 08:41:35 kanga smbd[1931]: [2011/07/20 08:41:35.885089, 0]
> smbd/server.c:281(remove_child_pid)
> Jul 20 08:41:35 kanga smbd[1931]: Could not find child 4219 -- ignoring
> Jul 20 08:43:31 kanga init: Id "co" respawning too fast: disabled for 5
> minutes
> Jul 20 08:50:12 kanga init: Id "co" respawning too fast: disabled for 5
> minutes
> Jul 20 08:54:36 kanga smbd[1931]: [2011/07/20 08:54:36.514163, 0]
> smbd/server.c:281(remove_child_pid)
> Jul 20 08:54:36 kanga smbd[1931]: Could not find child 4276 -- ignoring
> Jul 20 08:56:53 kanga init: Id "co" respawning too fast: disabled for 5
> minutes
> Jul 20 09:03:34 kanga init: Id "co" respawning too fast: disabled for 5
> minutes
> Jul 20 09:15:56 kanga kernel: imklog 5.8.3, log source = /proc/kmsg started.
> Jul 20 09:15:56 kanga rsyslogd: [origin software="rsyslogd" swVersion="5.8.3"
> x-pid="1359" x-info="http://www.rsyslog.com";] start
> Jul 20 09:15:56 kanga kernel: [ 0.000000] Initializing cgroup subsys cpuset
> Jul 20 09:15:56 kanga kernel: [ 0.000000] Initializing cgroup subsys cpu
> Jul 20 09:15:56 kanga kernel: [ 0.000000] Linux version 2.6.39-2-amd64
> (Debian 2.6.39-3) (ben@decadent.org.uk) (gcc version 4.4.6 (
> Debian 4.4.6-6) ) #1 SMP Tue Jul 5 02:51:22 UTC 2011
> Jul 20 09:15:56 kanga kernel: [ 0.000000] Command line:
> BOOT_IMAGE=/boot/vmlinuz-2.6.39-2-amd64 root=UUID=4b562550-ccd9-4eb1-9390-1
> 00d89682711 ro quiet
>
>
>
> Any ideas on how to debug this further.
>
>
Reply to: