Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bruce.cs.monash.edu.au!merlin!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!wupost!decwrl!pa.dec.com!usenet.pa.dec.com!jkh From: jkh@morse.ilo.dec.com (Jordan Hubbard) Newsgroups: comp.os.386bsd.questions Subject: Re: At boot FreeBSD claims DX when it's a SX Date: 18 Mar 1994 17:01:12 GMT Organization: Digital Equipment Corporation, Galway Ireland Lines: 20 Distribution: world Message-ID: <JKH.94Mar18170113@morse.ilo.dec.com> References: <1994Mar16.182415.12608@palantir.p.tvt.se> NNTP-Posting-Host: morse.ilo.dec.com In-reply-to: lars@pp2.smc.south.telia.se's message of Wed, 16 Mar 1994 18:24:15 GMT In article <1994Mar16.182415.12608@palantir.p.tvt.se> lars@pp2.smc.south.telia.se (Lars Norman) writes: When powering up, my machine correctly states that it has a 486SX CPU. The problem comes at boot, when FreeBSD is doing some kind of "autodetect" of CPU-type. FreeBSD claims that the machine is an 486DX and a little bit later, when starting to use the aha0 and sd0 it reach a fatal error/trap and stops (I guess that's is where we start using the math-HW, that I don't have). Erm, no, actually. FreeBSD erroneously reports all 486 chips as "DX" chips (amusing on my 486sx laptop, but harmless) but doesn't actually do anything with the information, nor is there any floating point code in the kernel that would cause problems at that stage in either case, so I believe your trap to be unrelated. What is the fatal error trap you're getting? It sounds like all is not quite right with your controller, SCSI devices or SCSI bus termination. We did have a bug until very recently that caused the kernel to trap on a divide-by-zero if no devices were probed - could this be the case? Jordan