From owner-freebsd-hackers Sat Jun 3 09:23:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA01575 for hackers-outgoing; Sat, 3 Jun 1995 09:23:52 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA01548 for ; Sat, 3 Jun 1995 09:23:44 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08712; Sat, 3 Jun 1995 17:52:59 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA22665; Sat, 3 Jun 1995 17:52:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA18266; Sat, 3 Jun 1995 14:37:31 +0200 From: J Wunsch Message-Id: <199506031237.OAA18266@uriah.heep.sax.de> Subject: Re: hang problems To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 3 Jun 1995 14:37:31 +0200 (MET DST) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) In-Reply-To: <199506030911.CAA12950@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 3, 95 02:11:25 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1017 Sender: hackers-owner@freebsd.org Precedence: bulk As Rodney W. Grimes wrote: > [reboot hangs] > > Rod, ain't this your baby? > > Nope, my baby is very solid. It is either a ``well reboot'' or > ``won't reboot'', it is never a ``Every once in a while'' type > of problem. Aye, i see. Where does my problem belong to? Box is an EISA, some SiS chipset, ELSA Winner 1000 grfx (S3 86C928). Reboots normally work, but under some particular circumstances (e.g. if i call ``cpu_reset'' from DDB, after a panic or somesuch), it attempts to reboot, and finally just sits there and beeps. The beep code indicates that it didn't find its video adaptor. I have to hit reset then. This is (i think) still with a kernel that only uses the ``CPU shut down'' method. Hmmm... just looked up the kernel source. The CPU reset code is already in there, so now i'm not sure if the symptom still happens now. I'll watch out for it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)