Date: Sat, 17 Jun 2006 00:33:16 -0700 From: Matthew Navarre <mnavarre@cox.net> To: Micah <micahjon@ywave.com> Cc: questions@freebsd.org Subject: Re: Random panics on FreeeBSD 6.0 Message-ID: <A7666C7D-8D47-4941-B96D-AD02A60E8556@cox.net> In-Reply-To: <44938613.3050301@ywave.com> References: <DED9F0AB-B6A7-4769-8EB9-DD5D9F9AC094@cox.net> <44936624.80801@ywave.com> <FBE35CFE-4BE6-4028-8603-55EA6A7A4E0D@cox.net> <44938613.3050301@ywave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 16, 2006, at 9:33 PM, Micah wrote: > Matthew Navarre wrote: >> On Jun 16, 2006, at 7:17 PM, Micah wrote: >>> Matthew Navarre wrote: >>>> I've got an AMD Sempron machine running FreeBSD 6.0 that's been >>>> experiencing random panics while trying to build world. In fact >>>> it just paniced now, with no activity. >>>> The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 08100000 >>>> bad pte >>>> This started last night while I was portupgrading ruby and I got >>>> random apps segfaulting, mostly gcc, so I suspected bad memory. >>>> I installed new memory today, tried to buildworld. And *BAM* >>>> panic: bad pte >>>> I'm still guessing that this is a hardware problem, and not >>>> software but I'm not sure. If anyone can give me a clue I'd >>>> appreciate it. >>>> Machine details: >>>> AMD Sempron >>>> ECS K8M800-M2 mainboard >>>> 1 GB Kingston PC-3200. >>>> Thanks, >>>> Matt >>> >>> First, a quick Google of "bad pte" turns up some ideas. Try >>> disabling or changing APIC and/or ACPI settings. Make sure your >>> swap partition is error free and has enough room. Google a bit >>> more just on the lists.freebsd.org site for several possibilities. >> Yeah, I was wondering if it might be something in the BIOS >> settings. I'll google around and see what I find. I don't know if >> the first panic was a bad pte error since the machine was running >> headless. >>> >>> For hardware, you can try memtest86+ to check to make sure the >>> new memory is good. There are other stress tests you can run as >>> well - I usually use the ultimate boot CD for that stuff. Other >>> possible problems are faulty or too small power supply; too much >>> heat on CPU, RAM, or expansion boards; faulty expansion cards and/ >>> or components; or faulty hard drive. >> I kinda wondered if heat might be an issue, since it was kind of >> tucked away in a spot with bad airflow. I'll try the memtest >> thing. Is there a way to get the CPU temp in FreeBSD? > > As mentioned, mbmon might work, but don't think that CPU is the > only generator of heat. I had random reboots due to an overheating > graphics card once. A spot thermometer comes in handy at a time > like this. Eh. I think it's time to find the receipt and make the computer store fix this POS. I think that's the last time I buy cheap crap hardware. Thanks again, Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A7666C7D-8D47-4941-B96D-AD02A60E8556>