Date: Sat, 12 Mar 2005 21:05:11 -0800 From: Joshua Tinnin <krinklyfig@spymac.com> To: freebsd-hardware@freebsd.org Cc: Ben Haysom <ben.haysom@gmail.com> Subject: Re: Unclean Reboot For No Apparent Reason Message-ID: <200503122105.11957.krinklyfig@spymac.com> In-Reply-To: <200503122051.05166.krinklyfig@spymac.com> References: <d014caa50503070929239ee860@mail.gmail.com> <d014caa5050312075947122fdc@mail.gmail.com> <200503122051.05166.krinklyfig@spymac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 12 March 2005 08:51 pm, Joshua Tinnin <krinklyfig@spymac.com> wrote: > On Saturday 12 March 2005 07:59 am, Ben Haysom <ben.haysom@gmail.com> > wrote: > > On Sat, 12 Mar 2005 09:33:45 -0600, Vulpes Velox > > <v.velox@vvelox.net> > wrote: > > > On Mon, 7 Mar 2005 17:29:17 +0000 > > > Ben Haysom <ben.haysom@gmail.com> wrote: > > > > Hi > > > > > > > > A while ago I asked about my 5.3 machine which has taken to > > > > rebooting itself during a full portupgrade.Doesn't shut down > > > > properly - just resets. > > > > > > > > I was advised to try a few things. > > > > > > > > I've done memtest86 from CD, let it do 5 passes and it found no > > > > problems. I unplugged both CDs and the Floppy, and tried it, > > > > but still did the same. cpuburn seems fine. > > > > doing mbmon whilst executing the portupgrade -a command shows > > > > the temperature get to around 42.5 before it resets, but it can > > > > vary. > > > > > > > > I'm stuck now... any ideas? > > > > Ben Haysom > > > > > > Memory tests only proove that that the memory is good, not that > > > the hardware the ram is connected to is good. The same for > > > cpuburn. The best stress test is running a make buildword, a make > > > install for scilab, and a find /. If that does not do it, it is > > > most likely a intermitently flakey power supply. > > > > those things do not do it. > > but the maachine is always on and only ever resets during > > portupgrade -a. every time. > > Well, you might try logging the output and seeing if it's failing at > the same point each time - try it more than once, logging to two > different files. If it is, then you have a pretty good idea what's > going on. If not, it's probably a hardware problem (though possibly > not). Sorry, that sounds vague ... If it fails at the same point each time, you will have a good idea what's going on from where it's failing, and in that case it's probably a software problem of some sort. If it's not rebooting when you stress the hardware as with the above tests (like buildworld), it's probably not a hardware problem, but if portupgrade -a is failing at random points, then it could still be hardware-related. - jt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503122105.11957.krinklyfig>