Date: Mon, 29 Mar 1999 11:08:20 +0930 From: Greg Lehey <grog@lemis.com> To: Spirer-McNamee <spimac@yahoo.com>, freebsd-questions@FreeBSD.ORG Subject: Re: system hangs after successful install Message-ID: <19990329110820.S413@lemis.com> In-Reply-To: <19990328223156.28086.rocketmail@web115.yahoomail.com>; from Spirer-McNamee on Sun, Mar 28, 1999 at 02:31:56PM -0800 References: <19990328223156.28086.rocketmail@web115.yahoomail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 28 March 1999 at 14:31:56 -0800, Spirer-McNamee wrote: > I started out with the 3.1-RELEASE on cdrom. I would get what seemed like a > successful installation. The system would boot fine, and everything > appeared to work--ethernet, ppp, apache, perl, etc. Then, after a few > hours, the system would hang--it would just stop with no warnings, > requiring pressing the reset button to reboot. > > So I decided to try 2.2.8-RELEASE on cdrom. Same result. Installs fine, > seems to run fine, then hangs, seemingly at random. > > There doesn't seem to be a pattern as to what the system's doing when it > hangs. It hangs while it's busy handling cgi scripts, ftp stuff, telnet > stuff, etc; it also hangs, after a fresh reboot, when it's just sitting > there doing only its own internal stuff. > > I've tried many installations, including bare bones ones with no extra > ports, no ethernet setup, no ppp, just the os and its default daemons. Same > result. > > Here's my hardware: > Intel PII 350 > 6.4G Western Digital AC26400R > Shuttle Hot 661/p 440 BX main board (pci) > 64 M SDRAM > internal modem > Teac CD > NEC floppy > Trendware PCI network card (DEC-based) > Matrox G200 Video card > > All hardware appears to be recognized properly at start-up. > > I have run diagnostics on the hard drive and reformatted it. No bad blocks > are found by Western Digital's diagnostic utility. > > Can someone give me some clues about where to go from here? Could it be an > irq thing? Something related to pci? What am I missing? It's difficult to diagnose this kind of problem, but it's almost always mainboard hardware. It's seldom anything to do with the disk (you can have problems with the disks, too, of course, but the symptoms are different). The two most likely culprits are the memory and the BIOS settings. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990329110820.S413>