the role of the dstd
Hi
Since my asus laptop's acpi won't work decently in Linux (lid close won't generate event and such) I've been reading up and I've come to the conclusion that the problem must be a messed up DSTD.
I do have some questions about it, though.
For one, if the DSTD is part of the BIOS, how come windows does work, while it must rely on the same data (I haven't installed any drivers for power mgt yet lid close does work, and so do the volume butons) If windows knows something we don't, can't we get the correct data from there?
Kind regards,
J. Hendrickx, hoping to see my suspend to ram working someday
Quoted 2 lines
For one, if the DSTD is part of the BIOS, how come windows does work, while it must rely on the same data
I'm not an ACPI expert but here is my understanding. Hopefully it's close enough to reality that the experts need to make only minor corrections and can keep hacking.
Often, or rather always, the manufacturer tests the DSDT only with Windows. If Windows makes assumptions about how the DSDT code should be interpreted that are different from what Linux assumes, even if Linux's assumptions are compatible with the ACPI spec, then the DSDT might fail when run with Linux.
For example, Windows serializes (runs in one thread) procedures automatically, even if a procedure is labelled NotSerialized. But Linux ACPI, unless you pass a boot option to tell it to act like Windows, will not serialize those procedures, and each one can run in its own thread.
Therefore, race conditions from a sloppy DSDT, which might be hidden in Windows, are often exposed in Linux. And so S3 suspend might hang because of one of those races or locking problems. My old Thinkpad 600X improved its S3 suspend behavior somewhat when booting with the "Act like Windows" option.
ACPI development on Linux is often: "My laptop doesn't suspend in Linux" (for a modern laptop it's almost certain that it suspends in Windows) and then people finding what bug needs to be introduced into the Linux DSDT interpreter so that Linux can act just like Windows.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
Is this option "act like windows" really available? Is it a boot parameter?
Thanks in advance.
Quoted 39 lines · Sanjoy Mahajan
Quoted 2 lines
For one, if the DSTD is part of the BIOS, how come windows does work, while it must rely on the same data
I'm not an ACPI expert but here is my understanding. Hopefully it's close enough to reality that the experts need to make only minor corrections and can keep hacking.
Often, or rather always, the manufacturer tests the DSDT only with Windows. If Windows makes assumptions about how the DSDT code should be interpreted that are different from what Linux assumes, even if Linux's assumptions are compatible with the ACPI spec, then the DSDT might fail when run with Linux.
For example, Windows serializes (runs in one thread) procedures automatically, even if a procedure is labelled NotSerialized. But Linux ACPI, unless you pass a boot option to tell it to act like Windows, will not serialize those procedures, and each one can run in its own thread.
Therefore, race conditions from a sloppy DSDT, which might be hidden in Windows, are often exposed in Linux. And so S3 suspend might hang because of one of those races or locking problems. My old Thinkpad 600X improved its S3 suspend behavior somewhat when booting with the "Act like Windows" option.
ACPI development on Linux is often: "My laptop doesn't suspend in Linux" (for a modern laptop it's almost certain that it suspends in Windows) and then people finding what bug needs to be introduced into the Linux DSDT interpreter so that Linux can act just like Windows.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell,_WarCrimes inVietnam_, chapter 1.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html