From owner-freebsd-bugs  Tue Oct 24 18:44:46 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA16898
          for bugs-outgoing; Tue, 24 Oct 1995 18:44:46 -0700
Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA16879
          for <bugs@freebsd.org>; Tue, 24 Oct 1995 18:44:37 -0700
Received: from ast.com by relay1.UU.NET with SMTP 
	id QQzmxi15168; Tue, 24 Oct 1995 21:44:18 -0400 (EDT)
Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA29294
  (5.67b/IDA-1.5 for <@uunet:bugs@freebsd.org>); Tue, 24 Oct 1995 18:45:44 -0700
Received: from nemesis by trsvax.fw.ast.com with uucp
	(Smail3.1.29.1 #3) id m0t7urd-00007rC; Tue, 24 Oct 95 20:42 CDT
Received: by nemesis.lonestar.org (Smail3.1.27.1 #19)
	id m0t7ul9-000ItkC; Tue, 24 Oct 95 20:36 WET DST
Message-Id: <m0t7ul9-000ItkC@nemesis.lonestar.org>
Date: Tue, 24 Oct 95 20:36 WET DST
To: bugs@freebsd.org
From: uhclem%nemesis@fw.ast.com (Frank Durda IV)
Sent: Tue Oct 24 1995, 20:36:02 CDT
Subject: re: kern/770: Floppy kernel won't boot with T485 or IDT L2 cache FDIV032
Sender: owner-bugs@freebsd.org
Precedence: bulk

kern/770: Floppy kernel won't boot with T485 or IDT L2 cache FDIV032

If you recall, this was a problem where if you had a 486-based system with
a Intel 485 Cache module or a IDT L2 cache module, the boot floppy would
not boot unless you physically removed the cache module first.   (This
is a transparent cache system, and there are no BIOS controls needed to
manipulate or disable it.)

This problem first appeared in 2.0.5-ALPHA and has been present in all
SNAPs and releases since.  Until now.

For some reason, the 1022-SNAP floppy boots (circa Monday 1400CDT) fine on
these systems (I tested three different models today).  I also re-verified
that 1005 and 2.0.5-R fail on the exact same systems.

The only reason I went back to looking at this at all, was that I was
installing 2.0.5-R on a system and forgot about the cache module.  But
instead of hanging like all the other systems did, this system
(supposedly the same as two of the machines I was using) got a kernel
panic and dumped what might be useful information.   So I wanted to
run 1022 on it and get the panic info to hopefully narrow down where the
problem is.  But 1022-Monday-1400CDT (Geez, put a .1 on it or something)
boots successfully. 

So something changed between 1005 and 1022 in the boot.flp department that
makes things all better.  I hope somebody knows what the change was! :-)

I suspect that nobody knows since I haven't seen a notification on this
bug indicating that this issue was 'closed' or even 'analyzed'.

Oh, I didn't have a 1005 floppy handy, but if a panic display for the 1005
or 2.0.5-R kernel would be useful to somebody, let me know (private mail
please).


Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi"
or uhclem%nemesis@fw.ast.com (Sick Route)   | demand...  A SEGMENT REGISTER!!!"
...letni!rwsys!nemesis!uhclem               |"A what?"
...decvax!fw.ast.com!nemesis!uhclem         |"LETNi! LETNi! LETNi!"  - 1983