Date: Sun, 3 Dec 1995 14:16:28 -0600 (CST) From: Mark Hittinger <bugs@freebsd.netcom.com> To: bugs@freebsd.org Subject: re: Mission Impossible-style crashes on 2.1.0 Message-ID: <199512032016.OAA02789@freebsd.netcom.com>
next in thread | raw e-mail | index | archive | help
> From: uhclem%nemesis@fw.ast.com (Frank Durda IV) > ... > However, in the seven days since upgrading to 2.1.0, the same hardware > has experienced an average of 10 unexpected reboots, or just over > one a day. The systems with more load (news vs no news) crash more often. > ... > Then around 15 seconds after the system went dead, the screen cleared and > the system rebooted. > ... > instantly. The odd thing is the 15-second delay is consistent, > like it is deliberate. (I wonder if a panic is occurring and not > being displayed for some reason and the 15-second timer for > press a key to avoid a reboot is running.) Wonder if the 15 second thing is: options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device :-) In any event I see something similar on a heavy news box at my former employer. One box with heavy UUCP and mail activity stays up forever. Another box running INN and CERN will die inexplicably during news expire runs especially :-) I do not use MMAP. Do you use alias IP's for "virtual web sites" on your ethernet? My news drive is a 4gig seagate. I wonder if we could isolate a common thread between our two configurations. Regards, Mark Hittinger Netcom/Dallas bugs@freebsd.netcom.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512032016.OAA02789>