From owner-freebsd-hackers Thu Oct 5 03:44:03 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA03024 for hackers-outgoing; Thu, 5 Oct 1995 03:44:03 -0700 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA02979 for ; Thu, 5 Oct 1995 03:42:52 -0700 Received: by Sysiphos id AA01442 (5.67b/IDA-1.5 for hackers@freebsd.org); Thu, 5 Oct 1995 11:40:42 +0100 Message-Id: <199510051040.AA01442@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 5 Oct 1995 11:40:41 +0100 In-Reply-To: Brian Tao "Flaky reboot problem with this SP3G board" (Oct 4, 19:38) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Brian Tao Subject: Re: Flaky reboot problem with this SP3G board Sender: owner-hackers@FreeBSD.org Precedence: bulk On Oct 4, 19:38, Brian Tao wrote: } Subject: Flaky reboot problem with this SP3G board } On Tue, 3 Oct 1995, David Greenman wrote: } > } > Try just pressing "Enter". The machine actually does a 'halt', not a } > reboot, and it needs a before it will reboot. I don't think virtual } > console switching works at this stage, either, which explains why the machine } > appears dead. } } I hit Enter at first, then spacebar, then I tried the switch } virtual consoles, etc. But after some more fiddling last night, I } think it just might be the hardware itself. The machine was rebooted } five times after I did the installation last night. Twice it hung as } I described, twice it rebooted itself properly and once it cleared the } screen (as if to reboot) and then stayed there. After hitting the } hardware reset, I get a message saying the CMOS checksums don't match } (or something) and that it was reloading the factory defaults. Is } this a bad BIOS revision problem, or bad memory, or what? My SP3G doesn't reboot reliable anymore, after I installed a cheap SoundBlaster clone. I've got to hit reset in about three out of four reboots ... Didn't have time to check for the reaon. Might the kernel debugger still be able to give reasonable output in such a case ? Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html