Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!news.mathworks.com!newsfeed.internetmci.com!news.msfc.nasa.gov!cs.utk.edu!not-for-mail From: jfarmer@cs.utk.edu (JOHN FARMER) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Strange message on older BSDi system Date: 22 Aug 1996 10:56:44 -0400 Organization: CS Department, University of Tennessee, Knoxville Lines: 38 Message-ID: <4vhsfcINNop5@duncan.cs.utk.edu> NNTP-Posting-Host: duncan.cs.utk.edu Ok, I know that this is an older system (BSDi v1.1) but it really can't be taken down long enough to build a 2.x system... It's a 486dx50 on an EISA motherboard with the Opti chipset. 8 30-pin simm slots. Up until recently, it had 16mb of memory (4, 4x9-60 sims). I then added memory to it (4 more, 4x9-60 simms) and while the new ram passes POST, I keep getting the the following messages during boot: Aug 22 02:31:38 sabre kernel: Aug 22 02:31:38 sabre kernel: NMI port 61 b0, port 70 ff Aug 22 02:31:44 sabre root: Configuration changed: Aug 22 02:31:44 sabre root: 36c36 Aug 22 02:31:44 sabre root: < NMI port 61 a0, port 70 ff Aug 22 02:31:44 sabre root: --- Aug 22 02:31:44 sabre root: > NMI port 61 b0, port 70 ff I'm also getting "random" re-boots and more than "normal" core-dumps of applications. All of this does seen to be tied to the new memory, but I'm trying to pin it down so I can swap them for replacements if need be. I've tried moving the new simms around, but the above msgs stay the same. Any ideas? I would boot a dos floppy & run a ramtest, but it appears that the A: drive died sometime in the last year (the last time it was used...). Please reply to Jfarmer@cs.utk.edu or jfarmer@goldsword.com. Thanks John -- John T. Farmer, Jr. jfarmer@cs.utk.edu Full-time Daddy, Some-time Grad Student, Ask me about Internet Full-time wage slave, Wood butcher when I can. Access in East Tenn. My son's hero's are Capt. Jean Luc Picard, Norm Abrams, and Mr. Rogers!