From hsu@mail.clinet.fi  Wed Aug 19 02:20:11 1998
Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14787
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 19 Aug 1998 02:20:09 -0700 (PDT)
          (envelope-from hsu@mail.clinet.fi)
Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4])
	by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id MAA07355
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 19 Aug 1998 12:20:24 +0300 (EEST)
Received: (from hsu@localhost)
	by katiska.clinet.fi (8.9.0/8.9.0) id MAA16883;
	Wed, 19 Aug 1998 12:19:25 +0300 (EEST)
Message-Id: <199808190919.MAA16883@katiska.clinet.fi>
Date: Wed, 19 Aug 1998 12:19:25 +0300 (EEST)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: Problems with a 386-16
X-Send-Pr-Version: 3.2

>Number:         7678
>Category:       kern
>Synopsis:       Problems with a 386-16
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 19 02:30:01 PDT 1998
>Closed-Date:    Fri Mar 10 03:10:51 PST 2000
>Last-Modified:  Fri Mar 10 03:11:28 PST 2000
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2.6-STABLE i386
>Organization:
Clinet, Espoo, Finland
>Environment:

386-16, two ed ethernet cards (no effect removing them), two serial ports,
IDE disk, EGA display (motherboard built-in).  My home router, routing
a serial link to ethernet.

>Description:

I tried to upgrade this from an old 2.?-stable (at least a year old, it had
uptimes >400 days) to -stable, with following effects:

After -stable upgrade:

Everything gets bus erros on bootup, and it usually panics when init dies
with bus error, sometimes goes into a deadlock (console driver works, but
nothing happens).

I tracked this back by using boot floppies for 2.1.0, 2.2.5, 2.2.6 and
2.2.7 to see how old this is, but unfortunately it is very old:

2.1.0	Works (by a miracle I still have an 2.1.0 installation to ftp from)

2.2.5	Panics with page fault right after regognizing EGA display

2.2.6	sysinstall dies with bus error

2.2.7	Nothing happens after kernel load (deadlock)

>How-To-Repeat:

Find an old 386 host.  New ones don't seem to exhibit this, we have couple
of 386-40's and I think also one 386-33 which do work.

I remember that there was some bug in early 386 processors related to vm,
but that was workaroundable and FreeBSD definitely worked with it before,
ditto for Linux.  I do not know if this could be something related.
Another curiosity in the machine is the EGA display adapter.

I do remember someone else reporting the same problem lately with boot
floppy.

>Fix:
	
Workaround is to use obsolete OS version or switch to Linux or
SomeOtherBSDWhichMaybeWorks.  As I'm using it as a router only, I can make
it relatively safe other than kernel-related DoS bugs, and this one is not
definitely critical application.  I just would like to wipe the 2.1.0
distribution from disks at some point :)

>Release-Note:
>Audit-Trail:

From: Greg Lehey <grog@lemis.com>
To: hsu@clinet.fi, FreeBSD-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: kern/7678: Problems with a 386-16
Date: Thu, 20 Aug 1998 08:43:46 +0930

 On Wednesday, 19 August 1998 at 12:19:25 +0300, Heikki Suonsivu wrote:
 >
 >> Number:         7678
 >> Category:       kern
 >> Synopsis:       Problems with a 386-16
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       medium
 >> Responsible:    freebsd-bugs
 >> State:          open
 >> Quarter:
 >> Keywords:
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Wed Aug 19 02:30:01 PDT 1998
 >> Last-Modified:
 >> Originator:     Heikki Suonsivu
 >> Organization:
 > Clinet, Espoo, Finland
 >> Release:        FreeBSD 2.2.6-STABLE i386
 >> Environment:
 >
 > 386-16, two ed ethernet cards (no effect removing them), two serial ports,
 > IDE disk, EGA display (motherboard built-in).  My home router, routing
 > a serial link to ethernet.
 
 How much memory?
 
 Greg
 --
 See complete headers for address, home page and phone numbers
 finger grog@lemis.com for PGP public key

From: "Ted Mittelstaedt" <tedm@toybox.placo.com>
To: <freebsd-gnats-submit@FreeBSD.org>, <hsu@clinet.fi>
Cc:  
Subject: Re: kern/7678: Problems with a 386-16
Date: Thu, 9 Mar 2000 22:03:06 -0800

 I have seen this kind of problem before as well on older 386/16
 systems.  It began sometime in the 2.2 series of kernels.  In fact
 I think I submitted it as a pr that has subsequently been closed.
 
 I can confirm that this is not ram related - I've run all 2.2 series
 on 4MB.  (the systems were very slow, of course)
 
 I do however believe this is a CPU bug.  There is a well-known 80386
 bug only present in early 16's that broke FPU support.  (note that any
 surface-mount 386-16 is well after the bug was fixed)  There are probably
 other ones as well.  I believe that the triggering incident on this bug is
 a newer version of GCC, NOT the FreeBSD kernel.
 
 In my case, swapping out the 80386-16 CPU with another 80386-16 CPU fixed
 the problem.  (obviously it was a socketed CPU)  The only difference 
 between the CPU's was that they were manufactured in different geographical
 locations.  Otherwise both were marked as Intel CPU's.
 
 Ted
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Fri Mar 10 03:06:30 PST 2000 
State-Changed-Why:  
Are you happy with Ted's explanation? 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Mar 10 03:10:51 PST 2000 
State-Changed-Why:  
Ted's explanation looks reasonable and mail to the originator 
bounces. 
>Unformatted:
