Date: Tue, 21 Mar 2006 12:24:08 -0800 From: Nate Lawson <nate@root.org> To: fukui.FreeBSD@fanet.net Cc: freebsd-acpi@freebsd.org, bug-followup@freebsd.org Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot Message-ID: <442060E8.2000908@root.org> In-Reply-To: <200603211343.55664.jhb@freebsd.org> References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> <200603211343.55664.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Monday 20 March 2006 19:33, Mark Linimon wrote: >> Synopsis: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot >> >> Responsible-Changed-From-To: freebsd-i386->freebsd-acpi >> Responsible-Changed-By: linimon >> Responsible-Changed-When: Tue Mar 21 00:31:09 UTC 2006 >> Responsible-Changed-Why: >> Over to maintainer(s). >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=93963 > > The patch basically forces the use of ACPI 1.0 tables if the ACPI 2.0 table > pointer is NULL. This is really just more BIOS brain damage. Most of the > patch is to Intel's ACPI-CA code, so we need to see what they think about > this workaround. Fukui-san, Would you please submit the output of acpidump -t to the PR? This would help us understand the RSDT and XSDT on your machine. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442060E8.2000908>