Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usc!hela.iti.org!cs.widener.edu!dsinc!ub!csn!copper!mercury.cair.du.edu!mnemosyne.cs.du.edu!nyx!smace From: smace@nyx.cs.du.edu (Scott Mace) Newsgroups: comp.os.386bsd.bugs Subject: Re: intermittant reboots and lockups (follow up) Message-ID: <1993Mar1.232255.29475@mnemosyne.cs.du.edu> Date: 1 Mar 93 23:22:55 GMT References: <1993Feb28.164505.982@mnemosyne.cs.du.edu> Sender: usenet@mnemosyne.cs.du.edu (netnews admin account) Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept. Lines: 47 X-Disclaimer: Nyx is a public access Unix system run by the University of Denver for the Denver community. The University has neither control over nor responsibility for the opinions of users. It appears that the problem is with the ULSI (accidently stated as USI) Math co-processor. The technician at ULSI said that the pallete distortion and intermittant lockups are caused by the npx driver sending 287 code. Apparently the ULSI chip does not understand 287 code. My next question is: What is 287 code doing in 386bsd? In the npx driver is says soemthing like.... NPX driver Numeric Processor Extension 287/387. What would be the point of running a 287 with a 386??? Does the npx-0.3? solve this 287 conflict? In article <1993Feb28.164505.982@mnemosyne.cs.du.edu> smace@nyx.cs.du.edu (Scott Mace) writes: >I am experiencing intermittant reboots and lockups on a am386DX-40, >while under considerable load (compiles, xv sessions.) A related >problem is that the pallete on the xv window when it firs come up is >corrupted as well. When I start up an xv session from a remote machine >it works fine. I have eliminated the usr tree as a problem. I nfs >mounted it from a machine that works fine. > >My setup is as follows: >amd 386DX-40 >USI 387DX-40 ^^^ USLI >Orchid Pro deisgner IIs >AMI BIOS >Adaptec 1542B >wd8003 controller >8 meg ram >0.2.1 patchkit > >The machine I tested it against was identical except for it being a >Intel 386DX-33 and intel 387DX-33. > >I have tried all working CMOS setup combinations. I have isolated the >problem to either a hardware problem or a problem with the root >filesystem or the kernel. Scott Mace -- ********************************************************************* * Scott Mace internet: smace@nyx.cs.du.edu * * emace@tenet.edu * *********************************************************************