Date: 22 Oct 2003 09:51:21 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "Hicks, Raymond" <Raymond.Hicks@dhs.gov> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: Re: kernal panic when trying to recompile world or kernel Message-ID: <44ad7te5ye.fsf@be-well.ilk.org> In-Reply-To: <234DD3619C980047AE58D944F03C3F13EF908C@HQWIRMEXCH04.hq.ins> References: <234DD3619C980047AE58D944F03C3F13EF908C@HQWIRMEXCH04.hq.ins>
next in thread | previous in thread | raw e-mail | index | archive | help
"Hicks, Raymond" <Raymond.Hicks@dhs.gov> writes: > I was hoping to get some insight into what could be causing these issues. > Any thing you can do to help is appreciated. Here is the situation: > > I have an asus A7M-266D with dual athalon MP 1800+ and 1.5G of DDR 2100 > RAM. The machine has 3 120GIG IDE drives, one floppy and one CD drive. > Drives are western digital. The kernel is compiled for SMP and the release > is FREEBSD-5.1-RELEASE although sources were current till about June at > which time I moved and did not do much to system. Now I have gotten the > system out of storage and set it up .. it runs fine but I have recently > tried to cvsup then recompile world and I get: > > KERNEL PANIC with CPUID = 0 > lapic.id = 00000000 > > It seems like a random error in that it sometimes does it in 2 minutes and > other times it will go for almost 10 minutes. Once it happens, the machine > reboots. I originally thought this could be due to heat from processors so > I took measures to reduce heat. There are currently 2 fans pushing air into > the case and 3 fans plus 1 blower pulling air out of the case. Each CPU has > a new amd cpu fan with bearings and the temp is well within the limits of > normal operation. I am at a loss for this and was wondering if anyone had > any ideas on ways to fix / mitigate. Still sounds like some kind of hardware problem, because it runs fine as long as it isn't under pressure and fails in a different way each time. If it's always the same CPU, that may be a hint. Bad RAM is the most frequent culprit for such unpredictable problems, though. If you have the opportunity to disable SMP and try again (e.g., you have a GENERIC kernel around that matches your userland), that would be worth a shot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44ad7te5ye.fsf>