Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: acpicpu(4) strangeness

> On Fri, Jan 28, 2011 at 09:18:14AM -0800, Dustin Marquess wrote:
> > So I managed to pull the ACPI data off of that one.  I'm hoping that
> > being a dom0, that the Xen hypervisor hopefully didn't fiddle with
> > things?  If so, I'll see if I can manage to get it booted clean.
> > Attached is the output.
> Thanks, those were just fine.
> The tables confirm that this is indeed a BIOS bug:


> Generally, there are couple of general options here:
>   1. Add a quirk for this board and prevent acpicpu(4) from loading.
>       For this, can you install sysutils/dmidecode and send the output?
>   2. Try to do the same guessing as the old EST. This would be a hack.

Is the bug in the ACPI table? If so, I seem to remember an option to load 
patched ACPI tables from the root file system.


Home | Main Index | Thread Index | Old Index