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.00] Initializing cgroup subsys cpuset Jul 20 09:15:56 kanga kernel: [0.00] Initializing cgroup subsys cpu Jul 20 09:15:56 kanga kernel: [0.00] Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@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.00] 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.bsf.2.00.1107200503190.64...@freire1.furyyjbeyq.arg
Re: Computer Freezes - how to find out what happened?
On 20/07/11 10:07, Jude DaShiell wrote: 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. It is not screensaver related. It was the first thing I thought of and disabled the screensaver. A few minutes ago it locked whilst I was moving the mouse. I don't think it is heat related either. I have a temperature gauge on my computer case and a sensor mounted in the centre of the fan on top of the CPU. In the old computer it ran at about 30degC this is currently showing at around 28degC. -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e269df4.4030...@chandlerfamily.org.uk
Re: Computer Freezes - how to find out what happened?
On Wednesday 20 July 2011 10:25:59 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.00] Initializing cgroup subsys cpuset Jul 20 09:15:56 kanga kernel: [0.00] Initializing cgroup subsys cpu Jul 20 09:15:56 kanga kernel: [0.00] Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@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.00] 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. Do you have any mean to ssh into it when it freezes? Thierry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107201124.39308.tchate...@free.fr
Re: Computer Freezes - how to find out what happened?
Alan Chandler a...@chandlerfamily.org.uk writes: 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 Take out the graphics card and put it back in. Don't run X and let it sit, with something like tail -f /var/log/syslog running on the console and see if it freezes. Perhaps the mainboard is broken. -- html messages are obsolete -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87fwm1z2ml@yun.yagibdah.de
Re: Computer Freezes - how to find out what happened?
On 20/07/11 11:07, lee wrote: Alan Chandlera...@chandlerfamily.org.uk writes: 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 Take out the graphics card and put it back in. Don't run X and let it sit, with something like tail -f /var/log/syslog running on the console and see if it freezes. Perhaps the mainboard is broken. I did have an extra graphics card in the machine and took it out. Now the only graphics is the integrated graphics chipset (Intel Sandybridge H67). I could try and run without X (I can do that by booting into recovery mode) - but I will have to wait until I am less busy. What I am really looking for is some log I can look at that gives me a clue as to what went wrong. At the moment I can find anything thing as to what the cause might have been -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e26b684.6050...@chandlerfamily.org.uk
Re: Computer Freezes - how to find out what happened?
I should have sent this reply to the list - I am doing so now On 20/07/11 10:24, Thierry Chatelet wrote: On Wednesday 20 July 2011 10:25:59 Alan Chandler wrote: ... 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. Do you have any mean to ssh into it when it freezes? Thierry Yes, but as you can see, when I try I can't connect. This tells me it is not just X freezing (because if X freezes I can ssh into the machine). -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e26b6ec.7040...@chandlerfamily.org.uk
Re: Computer Freezes - how to find out what happened?
Alan Chandler, 20.07.2011: 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.00] Initializing cgroup subsys cpuset Jul 20 09:15:56 kanga kernel: [0.00] Initializing cgroup subsys cpu Jul 20 09:15:56 kanga kernel: [0.00] Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@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.00] 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. Googling Id co respawning , I get many hits. Only checked the first and third for me, and they both suggested ways to get rid of that. http://forums.devshed.com/linux-help-33/id-co-respawning-too-fast-disabled-for-5-minutes-383777.html http://www.linuxquestions.org/questions/fedora-35/init-id-co-respawning-too-fast-disabled-for-5-minutes-736393/ If you can get rid of that message and still have the freeze, then at least we'll have that ruled out. By the way, instead of pushing the reset key, have you tried rebooting with the Alt-SysRq-B combo? (Or maybe the Alt-SysRq-REISUB version is better, pausing a few seconds between each letter.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720131652.gb32...@cs.utexas.edu
Re: Computer Freezes - how to find out what happened?
Did you do some stress test of your new hardware? If the problem is due to hardware problems you may not see anything in the log files. An example stress test is the compilation of the kernel or the sources of the gcc on the console without starting X. Query the web for signal 11. -- Best regards, Jörg-Volker. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j06n0t$lth$1...@dough.gmane.org
Re: Computer Freezes - how to find out what happened?
On 20/07/11 09:25, 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. It is too early yet to be super confident, but this morning I was freezing about every hour or so. At lunch time I upgraded the BIOS to solve (or rather it didn't solve = but thats another question) a video problem and I have been running for the last 4 or 5 hours without any freezes what so ever. Lets hope that it is working OK now. -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e270f21.4040...@chandlerfamily.org.uk
Re: Computer Freezes - how to find out what happened?
On Wed, Jul 20, 2011 at 06:23:45PM +0100, Alan Chandler wrote: On 20/07/11 09:25, 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. It is too early yet to be super confident, but this morning I was freezing about every hour or so. At lunch time I upgraded the BIOS to solve (or rather it didn't solve = but thats another question) a video problem and I have been running for the last 4 or 5 hours without any freezes what so ever. Lets hope that it is working OK now. If the problem persists, try running memtest to see if you've got a bad stick of RAM. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720222149.gg10...@aurora.owens.net
Re: Computer Freezes - how to find out what happened?
Jude DaShiell jdash...@shellworld.net writes: 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. How would that fix anything? -- html messages are obsolete -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874o2g5id1@yun.yagibdah.de
Re: Computer Freezes - how to find out what happened?
Alan Chandler a...@chandlerfamily.org.uk writes: I could try and run without X (I can do that by booting into recovery mode) - but I will have to wait until I am less busy. Let it run over night or at other times when you're not using it. What I am really looking for is some log I can look at that gives me a clue as to what went wrong. At the moment I can find anything thing as to what the cause might have been There's probably no logfile because when the computer is frozen, it's not going to write to logfiles anymore. -- html messages are obsolete -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zkk842p3@yun.yagibdah.de
