http://bugzilla.kernel.org/show_bug.cgi?id=9528
------- Comment #77 from [EMAIL PROTECTED] 2008-01-08 17:08 ------- That's how I read it as well, so I agree (I think any confusion boils down to lower power state = higher D-state value) - this really hasn't changed at all. Basically, the issue now as I see it is: 1) We must call _PTS() before we start putting the devices into their low power states (so the suspend re-ordering patches are correct). 2) Len is right to bring up USB though, in the sense that this is the one device that could be in a higher (aka lower power) D-state before we reach _PTS(), and on this chipset it's known to cause problems with the BIOS. On the nVidia chipsets (at least the CK804 - although I'm wondering if this also effects the Asus P1-AH2 we saw, which was also an nVidia board...) with these bad BIOS's, we may also need to stop ohci-hcd autosuspend to make sure we don't inadvertently move to a higher D-state early and trigger the hang that way (and it's possible Windows may also do this; Rafael, you mentioned before you had a CK804 board somewhere? It may be worth checking to see what a fully patched Vista or XP set USB autosuspend to on it for comparison). I think it's also becoming clear why _PTS() was changed in ACPI 2.0 - since (ab)uses like this are clearly possible with 1.0... -- 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, or are watching someone who is. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
