On Wed, 2010-06-02 at 23:10 +0800, Alan Stern wrote: > On Wed, 2 Jun 2010, Zhang Rui wrote: > > > On Wed, 2010-06-02 at 09:32 +0800, Alan Stern wrote: > > > On Wed, 2 Jun 2010, Zhang Rui wrote: > > > > > > > On Tue, 2010-06-01 at 21:11 +0800, Alan Stern wrote: > > > > > My kernel log is full of hundreds of messages like these: > > > > > > > > > > ACPI Exception: AE_AML_BUFFER_LIMIT, Index (000000046) is beyond end of object (20090903/exoparg2-445) > > > > > ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.STBR] (Node f701c918), AE_AML_BUFFER_LIMIT > > > > > ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node f7017b58), AE_AML_BUFFER_LIMIT > > > > > ACPI Error: Evaluating _BCM failed (20090903/video-528) > > > > > > > > > This sounds like a win7 compatibility issue that I've seen before. > > > > please try boot option acpi_osi="!Windows 2009" and see if it helps. > > > > > > Yes, indeed it does! It results in a few other differences too; I > > > can't tell whether they are good, bad, or neutral. > > > > > well, I don't see any other difference except some code execution > > ordering issue. > > You are right. Well, there is one difference: the lines about > "cfg80211: World regulatory domain updated:". I'm not concerned about > that. > > > I read the acpidump of this laptop, and it also confirms that this (_BCM > > stuff) is the only place that acpi_osi="!Windows 2009" changes. > > All right; I'll keep that boot config option. Is there a plan to fix > this compatibility issue? > This is a BIOS bug to me. The code runs in this way: if (not Win7) good BIOS code else buggy BIOS code This is a regression because ACPI declares it's win7 compatible in 2.6.31. I'm afraid we can do nothing in Linux kernel to fix/workaround it. IMO, we should ping Asus to fix it in their new BIOS release. thanks, rui We can not fix it in kernel. > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
