Date: Tue, 17 Apr 2001 22:30:54 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Mike Dorin" <bsd_mike@hotmail.com>, <lplist@closedsrc.org> Cc: <questions@FreeBSD.ORG> Subject: RE: Lockup problem continues...more info Message-ID: <005401c0c7c8$bcbf1580$1401a8c0@tedm.placo.com> In-Reply-To: <F92U0UJwUO06rKCIn7e0000b0be@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mike, Don't get too caught up in thinking that just because it fails on the same file all the time that the problem is reproducible. Your dealing with a random problem here, most definitely. I agree with Linh's suggestion to check for heat problems. However, let me caution you - if you do find an overheating component and correct the problem (by installing a new fan, or heatsink) don't be surprised if problems continue. Heat is a very bad thing for electronics - many components will be _permanently_ damaged by overheating, _espically_ if the overheating is chronic. Besides feeling the chips as he suggests, make sure to get a can of compressed air and blow out the computer. (what I do myself with my home server computers, which are running 24x7 is once a year I shut them down and haul them out to the driveway and pull off their cases then hit them with shop air from a blowgun - it's handy to have an air compressor in the garage. This is a good thing to do for monitors, too) The other suggestion for swapping the HD is a good one too - any old IDE drive even a small 1GB one will make a good test drive. Beyond that, here are some intermittent problems I've had in systems over the years and how I fixed them. Maybe you can get some use out of these. 1) Problem with OS/2 crashing intermittently on a 386 6MB system with an EGA adapter. (this was early 90's if I remember right) fixed with a different ega video card. problem ega card ran fine under Win 3.1 on a different system. 2) Problem with early BSD 0.1 crashing on a 8MB 386 Everex motherboard. Fixed the problem with changing a BIOS setting for the memory access speed. 3) Problem with early Fbsd 2.1.X series on a 486/33 system - swapped the CPU with another system and problem went away. (problem did NOT follow the CPU) 4) Problem with Win95 periodically locking up on a Pentium Pro system. Traced it to an ATI Ultra PCI video card - swapped ATI Ultra card with a ATI Rage 2 PCI card and it went away. Problem did NOT follow card. 5) Problem with NT locking up on a Pentium 166 motherboard, blamed it on NT and loaded BSD on the system. BSD started locking up too. Eventually found that if I removed all of the ISA cards from the system except for an Adaptec 1540 card, the problem went away. Changed the 2 NICS in the system (this is a router system) from SMC8013 isa nics to Realtek 8139 PIC cards and BSD stopped locking up. 6) Problem with a 486/66 16MB system running FreeBSD and locking up. Suspected a faulty disk controller because whenever the system crashed, and I rebooted it the filesystem was completely munged and irrecoverable. Tried 4 different IDE disks in the system with no different results. Finally put in a 1GB SCSI disk on an Adaptec 1520 SCSI controller and problem went away. Anyway, good luck with your system! Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Mike Dorin >Sent: Tuesday, April 17, 2001 1:23 PM >To: lplist@closedsrc.org >Cc: tedm@toybox.placo.com; questions@FreeBSD.ORG >Subject: Re: Lockup problem continues...more info > > >It seems to like to lockup mostly while I am building ssh_keygen.c. > >Also this time I got a panic! > >current process = 23319 (cc1) >interrupt mask = none >trap = 12 >panic: page fault > >Any ideas? >Thanks, >Mike > >>From: Linh Pham <lplist@closedsrc.org> >>To: Mike Dorin <bsd_mike@hotmail.com> >>CC: <tedm@toybox.placo.com>, <questions@FreeBSD.ORG> >>Subject: Re: Lockup problem continues...was memory tools >>Date: Tue, 17 Apr 2001 12:49:47 -0700 (PDT) >> >>On 2001-04-17, Mike Dorin scribbled: >> >># I thought that too. Except that it will for days without a problem >># if you don't do anything...except let it sit. >> >>When FreeBSD is idle, it sends an HLT instruction to the processor >>(except if you are using a multi-proc computer) to HALT or temporarily >>power down portions of the CPU to keep it cool and keeps the power >>consumption down. >> >>That is why the machine can be stable for a long time if you don't do >>anything taxing on it. Once you do a processor intensive process (like >>building a kernel or something like XFree86, [X]Emacs, make world, etc., >>the OS will not send [nearly as many] HLT instructions to the processor, >>so the processor is grinding away without a chance to cool off. >> >>-- >>Linh Pham >>[lplist@closedsrc.org] >> >>// 404b - Brain not found >> > >_________________________________________________________________ >Get your FREE download of MSN Explorer at http://explorer.msn.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > 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?005401c0c7c8$bcbf1580$1401a8c0>