Date: Wed, 19 Aug 1998 12:19:25 +0300 (EEST) From: Heikki Suonsivu <hsu@clinet.fi> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/7678: Problems with a 386-16 Message-ID: <199808190919.MAA16883@katiska.clinet.fi>
next in thread | raw e-mail | index | archive | help
>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. >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 :) >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808190919.MAA16883>