On Thu, Jun 16, 2011 at 09:48:59AM -0400, Phillip Susi wrote: > On 06/15/2011 11:44 AM, Matthew Garrett wrote: > >Well, that's the usual use-case for WoL. If you don't want a device to > >wake up from a specific sleep state, disable that device before entering > >that sleep state. > > I am reading reports from some users that their laptop keeps the > ethernet interface powered on and runs down the battery after shutting > down. It seems they are capable of waking the system from S5. It > appears that if the interface is not ethdown'ed in /etc/init.d/halt, > then it remains on. Are you saying that it is up to userspace to > disable WOL and down the interface before shutting down? Yes. How would the kernel know that you don't want WoL in that case? > Also strangely, ethtool reports that WOL is enabled for magic packet > ( which I guess comes from the bios default, I checked my desktop > and it also appears to default to wol: g, but can only wakeup from > s4 ), but /proc/acpi/wakeup claims wakeup for the device is > disabled. They should always agree shouldn't they? They should - failure to do so seems like a bug. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
