Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Dec 1995 13:13:11 -0800
From:      David Greenman <davidg@Root.COM>
To:        uhclem%nemesis@fw.ast.com (Frank Durda IV)
Cc:        bugs@freebsd.org
Subject:   Re: Mission Impossible-style crashes on 2.1.0 
Message-ID:  <199512032113.NAA00641@corbin.Root.COM>
In-Reply-To: Your message of "Sat, 02 Dec 95 11:59:00 %2B0700." <m0tLwDO-000C0aC@nemesis.lonestar.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
>I have several systems (6) that I recently upgraded to 2.1.0-RELEASE.
>These systems all ran 2.0.5 previously, and had no crashes in at
>least the previous 90 days (very nice).
>
>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.

   A couple of observations... If you've had "only" 10 unexpected reboots
across 6 machines and that it happens  more often on heavy-load machines,
does this suggest that some of the machines aren't crashing at all?

>Finally it happened in front of me on one of the systems.  The system was
>reasonably idle (tind was active and I was in vi writing and no X), when
>the console keyboard went dead.  All the keyboard lights turned off
>(NUM LOCK is normally on) and disk activity stopped.  I tried changing
>screens and hitting a few keys like NUM LOCK, but no action.  I then
>unplugged and reconnected the keyboard.  That didn't help either.
>Then around 15 seconds after the system went dead, the screen cleared and
>the system rebooted.

   Do you use a screensaver on your machines?

-DG



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512032113.NAA00641>