Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!xlink.net!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: 2.0.5 kernels aren't working
Date: 29 Jun 1995 12:11:24 +0200
Organization: Private U**x site, Dresden.
Lines: 20
Message-ID: <3stu8c$b45@bonnie.tcd-dresden.de>
References: <3srn96$hdb@toads.pgh.pa.us>
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
Bob Kramer <kramer@cs.pitt.edu> wrote:
> I am having some major-league problems with the kernel for 2.0.5. The
>RELEASE kernel panics and reboots at random times due to an I/O channel check.
IO channel check conditions are caused by lowering a signal on the ISA
bus (offhand i think it's line B1), that will cause an NMI to the CPU.
Looks like you've got perhaps some device that is triggering this line
accidentally?
There's also the opportunity that the FreeBSD kernel were misinter-
preting the NMI status registers, and the actual error might be an NMI
due to memory parity errors. The IO channel checks should happen
under DOS as well, while the parity errors might be generated from a
SIMM that's not used by DOS at all.
--
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. ;-)