Date: Tue, 29 Nov 2005 14:52:34 -0500 From: John Baldwin <jhb@freebsd.org> To: David Kelly <dkelly@hiwaay.net> Cc: freebsd-acpi@freebsd.org Subject: Re: Worked in RELENG_5, fails in RELENG_6 Message-ID: <200511291452.35400.jhb@freebsd.org> In-Reply-To: <804E027B-1274-40E2-8691-F6B6D057BC0A@hiwaay.net> References: <20051127010724.GA1161@Grumpy.DynDNS.org> <200511280813.59911.jhb@freebsd.org> <804E027B-1274-40E2-8691-F6B6D057BC0A@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 28 November 2005 10:46 pm, David Kelly wrote: > On Nov 28, 2005, at 7:13 AM, John Baldwin wrote: > > On Saturday 26 November 2005 08:07 pm, David Kelly wrote: > >> Per instructions at > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi- > >> debug.html > >> > >> System is Dell Poweredge 400SC, BIOS revision A06. Boot panics > >> with ACPI > >> enabled. > >> > >> boot -v: > >> [too much to type] > >> ACPI-0237 *** Error: Incorrect table signature - wanted [FACS] > >> found [ ] > >> ACPI-0359 *** Error: Could not get/install the FACS, AE_BAD_SIGNATURE > >> ACPI-0191 ... > >> ACPI-0213 ... > >> ... > >> panic: Using MADT but ACPI doesn't work. > >> > >> Have not figured out how to "boot -v" with ACPI disabled. That > >> would be > >> a nice little thing to add to chapter 11.16.1 of the Handbook. > > > > At the loader prompt, do: > > > > 'set hint.acpi.0.disabled=1' > > > > and then 'boot' or 'boot -v'. > > Downloaded and FLASHed BIOS from A06 to Dell's latest, A09 this > evening. No improvement. Also built and installed a new kernel from > cvsup this afternoon. No improvement. But 5.4 works fine with ACPI enabled? This is the machine that even acpidump chokes on, yes? Does acpidump work ok on 5.4? > A curious thing is with HT disabled in BIOS FreeBSD still lists > hyperthreading in the CPU capabilities. Not curious at all. The BIOS setting just has the BIOS mark HTT CPUs as disabled in the ACPI MADT table (usually HTT CPUs aren't even listed in the MP Table). > Oh, and apparently the dmesg buffer isn't big enough to hold > everything "boot -v" wants to say. Surely there is a way to make it > bigger? Well, using a serial console is the best method, but there is also a kernel option for increasing the message buffer size documented in sys/conf/NOTES. -- 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?200511291452.35400.jhb>