http://bugzilla.kernel.org/show_bug.cgi?id=12873
--- Comment #62 from ykzhao <yakui.z...@intel.com> 2009-07-22 06:07:55 ---
Hi, Kenney
Thanks for the test.
From the info in comment #52 it seems that irq is not disabled in the boot
phase with the boot option of "acpi_osi=linux" or acpi_osi="!Windows 2006"
acpi_osi="!Windows 2006 SP1". The second issue is the low memory corrupt after
suspend/resume. This should be related with BIOS bug.
Of course I can add the box to the DMI quirk table about low memory
corruption.
After adding the acpi_osi boot option, the following in the _PSW object
won't be executed:
>If (LEqual (TPOS, 0x40))
{
Store (Arg0, \_SB.PCI0.SMB.WOLF)
}
In such case OS won't complain that the irq 9 is disabled. And from the AML
code we know that the WOLF is accessed by using the I/O port behinds the
LPC(SMB) bridge. Maybe the WOLF will change the interrupt polarity of ACPI
interrupt 9.
Before the commit 729b2bd is shipped, it won't call the _PSW object unless
when it enters the suspend/resume. In such case the ACPI interrupt mode is
low/level.
But after the commit is shipped, OS will call the _PSW object for PB6
device. In such case the ACPI interrupt mode should be level/high. And from the
test it seems that this issue can be workaround by adding the boot option of
"acpi_osi=".
So I will add this box to the dmi quirk table to enable linux osi.
Thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.
------------------------------------------------------------------------------
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
