From owner-freebsd-hackers Sun Dec 8 14:23:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA26841 for hackers-outgoing; Sun, 8 Dec 1996 14:23:31 -0800 (PST) Received: from netrover.com (ottawa24.netrover.com [205.209.19.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA26835 for ; Sun, 8 Dec 1996 14:23:16 -0800 (PST) Received: (from brianc@localhost) by netrover.com (8.8.2/8.8.2) id RAA00265; Sun, 8 Dec 1996 17:22:16 -0500 (EST) Message-ID: Date: Sun, 8 Dec 1996 17:22:15 -0500 From: brianc@netrover.com (Brian Campbell) To: freebsd-hackers@freebsd.org (FREEBSD-HACKERS-L) Subject: Re: Odd booting problems with 2.2-ALPHA References: X-Mailer: Mutt 0.51 Mime-Version: 1.0 Reply-to: brianc@pobox.com In-Reply-To: ; from Brian Tao on Dec 8, 1996 15:07:15 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao writes: > I recently installed 2.2-ALPHA on a handful of new workstations > around the office, and noticed problems related to the boot procedure. > The hardware is an Intel P166 on a Gigabyte 430VX motherboard: > > ... > > All the machines have experienced one of the two problems I want > to describe. On random occasions when rebooting, the machine will > simply freeze just after the initial kernel load message and before it > prints the BIOS memory size check (the first line printed in bright > white with the syscons driver). This can happen from power-on, coming > from a DOS session, or rebooting from FreeBSD. My Dell P166 running 2.2-alpha has done this too on occasion. However I haven't been able to find a repeatable set of circumstances under which it happens. However, if it happens, it's usually right after powerup and the floppy light is still on from the bios "probes". Perhaps it's an unexpected interrupt.