[Gllug] Mysterious reboots

Tue Apr 4 12:02:44 UTC 2006

I'd try variations of:

If using an SMP kernel try a non-SMP kernel.
Removing all PCI cards and any USB devices that aren't essential.
Changing the graphics card or using onboard if available.

I had an Athlon that intermittently crashed like this, I think it was a 
graphics card issue - but it could be many things...

>From: will <will at willj.net>
>Reply-To: Greater London Linux User Group <gllug at gllug.org.uk>
>To: "gllug >> Greater London Linux Users Group" <gllug at gllug.org.uk>
>Subject: [Gllug] Mysterious reboots
>Date: Tue, 04 Apr 2006 12:53:19 +0100
>
>Hello.
>
>I hope someone here has some idea of what the problem with my computer is, 
>I have no idea.
>
>I have a new machine at work (AMD Athlon(tm) 64 Processor 3200+, 2Gb dual 
>channel memory).  It was working fine for a few weeks but now I have a 
>really big problem.  Seemingly at random the machine hangs for about 10 
>seconds (frozen display) then reboots (not a graceful reboot, just back to 
>the BIOS).  Sometimes it goes for hours without this happening (it stayed 
>up all last weekend), and sometimes it will reboot frequently (10 times 
>yesterday).
>
>As I mentioned, it was working fine.  Some things I had considered might 
>have contributed to the problem, ie. the machine was fine before I did 
>these things:
>
>1) I upgraded to FC5 from FC5 test3
>2) I moved /home from /dev/hda<something> to a software raid mirror 
>consisting of /dev/sda2 (SATA) and /dev/hda1
>
>I have now reversed 2) and he machine has since crashed/rebooted.
>
>Also I have also considered the following possible causes:
>
>1) Overheating?: however lm_sensors indicates the temperatures in the 
>case/CPU to be a fairly constant 32 deg/c
>2) Lack of power?: reboots have happened during prolonged periods of CPU 
>idleness and the machine only has a low-spec gfx card and two HD's in, the 
>400Watt power supply should be able to cope.
>3) The power in the building could be crap: however no-one else in the 
>building seems to have these problems
>4) My power supply may have developed a fault.
>
>A colleague has a machine with the same CPU and two HD's in it and has had 
>no problems (although he is running 32bit windowsXP), and no-one else in 
>the building is reporting problems.
>
>The last reboot I had was about 12:00 midday, the one before that about 
>6:00 PM last night.  Yesterday the machine rebooted about 10 times.
>
>Can anyone suggest any things I should test for or what could be wrong?  It 
>seems to me to be a hardware fault, but I could be wrong.  Has anyone else 
>experienced these sort of problems?
>
>This is the Motherboard I have, if it makes any difference:
>
>http://www.microdirect.co.uk/ProductInfo.aspx?ProductID=10165&GroupID=1091
>
>And here is /var/log/messages spanning the last reboot.  As you can see the 
>last activity before the reboot was at 11:37:06 and there were no errors 
>reported.
>
>Apr  4 09:55:05 localhost dhclient: DHCPREQUEST on eth0 to 192.168.10.69 
>port 67
>Apr  4 09:55:05 localhost dhclient: DHCPACK from 192.168.10.69
>Apr  4 09:55:05 localhost dhclient: bound to 192.168.10.220 -- renewal in 
>1441 seconds.
>Apr  4 10:19:06 localhost dhclient: DHCPREQUEST on eth0 to 192.168.10.69 
>port 67
>Apr  4 10:19:06 localhost dhclient: DHCPACK from 192.168.10.69
>Apr  4 10:19:06 localhost dhclient: bound to 192.168.10.220 -- renewal in 
>1376 seconds.
>Apr  4 10:33:51 localhost avahi-daemon[2190]: Recieved repsonse with 
>invalid source port 4576 on interface 'eth0.0'
>Apr  4 10:42:02 localhost dhclient: DHCPREQUEST on eth0 to 192.168.10.69 
>port 67
>Apr  4 10:42:02 localhost dhclient: DHCPACK from 192.168.10.69
>Apr  4 10:42:02 localhost dhclient: bound to 192.168.10.220 -- renewal in 
>1550 seconds.
>Apr  4 11:07:52 localhost dhclient: DHCPREQUEST on eth0 to 192.168.10.69 
>port 67
>Apr  4 11:07:52 localhost dhclient: DHCPACK from 192.168.10.69
>Apr  4 11:07:52 localhost dhclient: bound to 192.168.10.220 -- renewal in 
>1754 seconds.
>Apr  4 11:37:06 localhost dhclient: DHCPREQUEST on eth0 to 192.168.10.69 
>port 67
>Apr  4 11:37:06 localhost dhclient: DHCPACK from 192.168.10.69
>Apr  4 11:37:06 localhost dhclient: bound to 192.168.10.220 -- renewal in 
>1416 seconds.
>Apr  4 11:57:00 localhost syslogd 1.4.1: restart.
>Apr  4 11:57:00 localhost kernel: klogd 1.4.1, log source = /proc/kmsg 
>started.
>Apr  4 11:57:00 localhost kernel: Bootdata ok (command line is ro 
>root=LABEL=/1 rhgb quiet)
>Apr  4 11:57:00 localhost kernel: Linux version 2.6.16-1.2080_FC5 
>(bhcompile at hs20-bc1-4.build.redhat.com) (gcc version 4.1.0 20060304 (Red 
>Hat 4.1.0-3)) #1 SMP Tue Mar 28 03:38:47 EST 2006 Apr  4 11:57:00 localhost 
>kernel: BIOS-provided physical RAM map:
>Apr  4 11:57:00 localhost kernel:  BIOS-e820: 0000000000000000 - 
>000000000009ec00 (usable)
>Apr  4 11:57:00 localhost kernel:  BIOS-e820: 000000000009ec00 - 
>00000000000a0000 (reserved)
>Apr  4 11:57:00 localhost kernel:  BIOS-e820: 00000000000e8000 - 
>0000000000100000 (reserved)
>Apr  4 11:57:00 localhost kernel:  BIOS-e820: 0000000000100000 - 
>000000007ffb0000 (usable)
>Apr  4 11:57:00 localhost kernel:  BIOS-e820: 000000007ffb0000 - 
>000000007ffc0000 (ACPI data)
>
>Thanks,
>Will.
>--
>Gllug mailing list  -  Gllug at gllug.org.uk
>http://lists.gllug.org.uk/mailman/listinfo/gllug

-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug