Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: INTERRUPT 16 boot hang
Date: 20 Jul 1995 10:48:36 +0200
Organization: Private U**x site, Dresden.
Lines: 25
Message-ID: <3ul594$ib0@bonnie.tcd-dresden.de>
References: <3ugi16INNgv@scarecrow.mke.ab.com> <3uhu6u$m6l@news.bu.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In article <3uhu6u$m6l@news.bu.edu>, Mikhail Teterin <mi@csb.bu.edu> wrote:
>Some time ago (18 Jul 1995 14:55:34 GMT) honorable Thad Phetteplace x4461,
>residing at tdphette@mke.ab.com wrote:
>|I am upgrading a FreeBSD 1.5.1.1 system to 2.0.5. The install process
>|works fine, but then the system hangs during boot with the following
>|message:
>
>|npx0: INTERRUPT 16
>
>npx0, AFAIK, stands for numeric co-processor.
His problem is not likely related to the npx or something like this.
There's a long `pause' just after the announcement of npx0, and many
things happen there (configuration of internal devices, configuring
the system's console, mounting root, forking the first processes etc.)
until finally init will fork the /etc/rc (or single-user) shell which
is the first publically visible operation again.
Many possible reasons, and no really clue by me. That's why i've been
silent.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)