From owner-freebsd-stable Fri May 7 11:57:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id B8F6214BC9 for ; Fri, 7 May 1999 11:57:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01003; Fri, 7 May 1999 11:55:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905071855.LAA01003@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Greg Quinlan" Cc: "Joseph Jacobson" , freebsd-stable@FreeBSD.ORG Subject: Re: Strange reboot saga In-reply-to: Your message of "Tue, 11 May 1999 17:27:12 BST." <014f01be9bcb$2200d9a0$380051c2@greg.qmpgmc.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 11:55:29 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A totally spontaneous reboot, with absolutely no console output whatsoever is almost certainly a hardware problem. FreeBSD _will_not_ reboot without telling you about it; in some extreme cases you will get a very terse message (usually indicating kernel stack overflow) but you will _always_ get something. So if you're rebooting with _no_ console output at all, look to your hardware. > I am looking like an idiot! I have pushed and pushed to get FreeBSD > installed as the replacement > primary servers. (DNS, Web, Firewall, E-Mail, NAT.....) Now ........... well > the rest is history............ > (3.1-Stable) > > 2 Days... reboot.... 2 Days.....reboot..... > Always around 16.29pm BST. > > No beep.....Same here!! > No Panic....Same here!! > Hangs.........Same here!! > Reboots......Same here!! > Starts up and runs perfectly....Same here!! > WTF... yes#!@? > > I have compiled ddb... and so on but have no idea what to do next! > > Greg > > -----Original Message----- > From: Joe Jacobson > To: freebsd-stable@FreeBSD.ORG > Date: 07 May 1999 15:45 > Subject: Strange reboot saga > > > > > >Came home a couple of days ago to my wife telling me that my 3.1-STABLE box > >rebooted on her when she was surfing. (She habitually causes netscape 4.5 > >to crash, but I thought the box going down was a bit strange.) I find the > >machine in a powered down state, bring it back up, and log in as myself. > >I immediately startx, the graphics mode changes, and then it hangs for a > >couple of seconds, and all of a sudden I'm looking at the boot message > >from my graphics card. No beep, no panic, just an instantaneous reboot. > >The machine comes back up, I log in as root, check the logs, (I'm keeping > >*.debug syslogs), dmesg, nothing. startx (as root), nothing. Log in as > >myself, startx, everything is great. I chalk it up to an act of Eris. > > > >Last night, I built the world, from sources two days ago. Everything went > >peachy. Recompiled the kernel, rebooted, the box comes up fine. Log in > >as myself, startx, it reboots. WTF? Watch the box come up again, log in > >as myself, startx, it reboots again. WTF?!?! I let the machine come up, > >and then go to bed, thinking I fscked up the installworld or something. > >Wake this morning, log in as root, check the logs, nothing. startx, works > >like a champ, logout, login as myself, startx, works great. > > > >If anyone is interested, I suppose I could compile a debugging kernel, > >reboot, and then startx.... > > > >-- > >Joseph Jacobson Finger for PGP > >#include > >Two men walk into a bar. The third one ducks. > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message