Date: Mon, 1 Mar 2004 16:39:20 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: current@freebsd.org Subject: Re: worst FreeBSD EVAR. (crash on boot) Message-ID: <200403011639.20379.jhb@FreeBSD.org> In-Reply-To: <20040228124235.GJ56622@elvis.mu.org> References: <20040228124235.GJ56622@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 28 February 2004 07:42 am, Alfred Perlstein wrote: > So I'm updating from a Dec 5th kernel to today's so as to hopefully > restore the cool pre-Dec 5th ACPI behaviour which was: > Hitting the power button did an orderly shutdown. > > Instead of Dec 5th's behaviour which is: > Randomly (well mostly when I fat finger ^A-n to switch screens) > failing to suspend to disk and then completely locking up. > Hitting power button does an immediate shutdown.. like power OFF, > no orderly shutdown, fsck at boot required, baby jesus cries etc. > > Well now I have a kernel that won't even boot, here's the dmesg > from the Dec 5th kernel with a marker where the panic happens on > the newer kernel (noted by: <<<PANIC HERE ON NEW KERNEL>>) any > help would be appreciated. > > Machine is an old laptop, a Dell Latitude, celeron 300, 128 megs > of ram. It seems to crash both with and without ACPI loaded now. > > pcib1: <PCIBIOS PCI-PCI bridge> at device 1.0 on pci0 > pcib1: secondary bus 1 > pcib1: subordinate bus 1 > pcib1: I/O decode 0xc000-0xcfff > pcib1: memory decode 0xfd000000-0xfeffffff > pcib1: prefetched decode 0xf9000000-0xfbffffff > pci1: <PCI bus> on pcib1 > pci1: physical bus=1 > map[10]: type 3, range 32, base fb000000, size 24, enabled > map[14]: type 1, range 32, base fdc00000, size 22, enabled > map[18]: type 1, range 32, base fdb00000, size 20, enabled > > > <<<PANIC HERE ON NEW KERNEL>> > trap 12, fault addr: 0xb1e2 > code @0xc00fc492 cmpb %cs:0xb1e2, %bh This code looks to be in the BIOS. Yep, fc492 is in the BIOS. You shouldn't be getting this panic with ACPI as we don't call the BIOS to route interrupts for the ACPI case. You are probably a victim of whatever broke BIOS32 calls in 5.x (all the way back to 5.0) that causes panics in the !ACPI PnP BIOS probe on 845 and 865-based motherboards. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403011639.20379.jhb>