On Fri, 18 Mar 2005 09:43 am, Voytek wrote: > <quote who="Ben de Luca"> > > > you already log this, run the command 'last' and have a look > > > > thats a confusing statement what i mean is, > > bash> last > > reboot ~ Thu Dec 2 15:00 > > shutdown ~ Thu Dec 2 14:59 > > bend ttyp5 Thu Dec 2 14:58 - shutdown (00:01) > > bend ttyp5 Thu Dec 2 14:58 - 14:58 (00:00) > > thanks, Ben > > # last | grep reboot > reboot system boot 2.4.20-28.7 Thu Mar 17 07:57 (1+01:41) > reboot system boot 2.4.20-28.7 Tue Mar 15 11:53 (2+21:44) > reboot system boot 2.4.20-28.7 Tue Mar 15 11:05 (2+22:33) > # last | grep shutdown > # > > so I had 3 reeboots in the last 3 days, bit of a worry
Indeed - 3 "boots" with no shutdowns or reboots. Normally this is a result of kernel panics. Have you changed anything recently - new kernel perhaps? Have you added any new equipment that might be loading a buggy driver? Often the kernel will panic when there's a physical problem with your hardware too - try reseating all your RAM and cables etc. Make sure your cooling fans are all working too (I've had a few machines panic when the CPU freezes due to over-temp etc.). Your machine is not well by the sound of things :( James -- Chicago law prohibits eating in a place that is on fire. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
