From owner-freebsd-current  Tue Jun 18 12:19:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA19306
          for current-outgoing; Tue, 18 Jun 1996 12:19:13 -0700 (PDT)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA19283
          for <freebsd-current@freefall.freebsd.org>; Tue, 18 Jun 1996 12:19:06 -0700 (PDT)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA28852; Tue, 18 Jun 1996 12:18:42 -0700
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199606181918.MAA28852@GndRsh.aac.dev.com>
Subject: Re: reboot beeps
To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies)
Date: Tue, 18 Jun 1996 12:18:42 -0700 (PDT)
Cc: freebsd-current@freefall.freebsd.org
In-Reply-To: <199606181805.UAA11040@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at "Jun 18, 96 08:05:06 pm"
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I installed a three days old kernel today - maybe one shouldn't do, eh?
> Anyway,  it costs me a drive to the campus at present when I
> type 
> 
> sync ; reboot
> 
> since it hangs with a black screen and beeps. This machine has been one
> of my most reliably remotely rebootable machines for over a year. I
> understand that there were changes in the keyboard reset code (delays etc.)
> but that it has to be broken so miserably...
> 
> I added a second WD8013 card though but I can't imagine that being the
> culprit.

Infact it is very likely the culprit.  This is a 16-bit shared memory
card, and you can not mix 8-bit and 16-bit memory access in the same
128K bios/shared memory area between 640K and 1M.

For example, if you have an 8-bit BIOS at C800 you can't put a 16-bit
shared memory card at CC00.  The symptoms of doing this are exactly what
you are getting.  A hard reset will cure it, as that usually disables the
shared memory on the SMC8013 until the driver turns it back on.

> 
> I'll build a very recent kernel now to see if it's still there.
> 
> --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
> 


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD