Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.mathworks.com!panix!ddsw1!usenet From: krnlhkr@mcs.com Newsgroups: comp.os.386bsd.bugs Subject: FreeBSD2.0 Lockup Date: 15 Feb 1995 06:15:04 GMT Organization: MCSNet Services Lines: 24 Message-ID: <3hs659$rcp@News1.mcs.com> NNTP-Posting-Host: krnlhkr.pr.mcs.net Keywords: FreeBSD 2.0 lockup bugs X-Newsreader: AIR News 3.X (SPRY, Inc.) Hi... I haven't posted here before and have just started reading here, so please excuse me if this has been brought up already. I've been having trouble with the 2.0 (jan 1995) WalnutCreek FreeBSD locking up on me. It seems like a deadlock problem with interrupts shut off. I believe interrupts are shut off because the system locks dead with no panic, and the num-lock/caps-lock keys don't light the LED's, there is no syncing or paging going on, etc. I have tried to diagnose the problem, but to no avail. I am running off 2 IDE hard drives, and have an adaptec 1542CF controller with a Toshiba 2X CD-ROM drive hooked up to it and a Wangtek 525MB SCSI tape backup. I've tried everything from catting /dev/rwd0d > /dev/null to recompiling a stripped kernel with the bare essentials in it. I've also monitored the free memory and paging, and can't find any correllation between those and the lockup. Oh yeah, it's a 386/40 w/ 16MB of ram and a 60MB swap partition. Any suggestions would be helpful. I'm willing to ftp a snapshot program, but before I ftp 30megs over a slip connection, I'd like to know if it can help my problem. If someone has seen this and knows if it is or is not fixed, please let me know (prefer posting so others can see the reply, but mail is OK, too). Also, is there a known bug list and where can I get a copy? Thanks! -Louis Giliberto krnlhkr@mcs.com (.sig under construction)