On Sat, 2012-02-25 at 23:48 -0800, Shannon Dealy wrote: > On Sun, 26 Feb 2012, Ben Hutchings wrote: > > > On Thu, 2012-02-23 at 17:59 -0800, Shannon Dealy wrote: > > [...] > >> some point, outside software MUST be providing bogus information to the > >> driver. I say this because after the deep sleep bug occcurs and the > >> hardware has been power cycled (through hibernate), the device driver and > >> firmware have been reloaded and right from the start they show the "deep > >> sleep" state again. > > > > For a complete power-cycle, you may need to remove both the power cord > > and the battery. I don't think the Intel wireless cards have any > > support for wake-on-WAN, but in general devices may still be partly > > powered as long as any power source is connected to the system. > > True enough, and I don't remember if I pulled the battery back when I was > going after this problem (it has been almost a year since I did all my > tests). There is also a switch on the side that kills all RF devices > (WLAN and Bluetooth) but I can't verify that it completely kills power to > the devices.
AFAIK the switch on Thinkpads does not kill power to the wireless card.
[...]
> > Having said that, are you setting the pcie_aspm kernel parameter?
>
> No, wasn't even aware of its existance. System shows it is currently at
> "default" unfortunately, the debug kernel I am currently running has the
> pcie_aspm regression which prevents it from being changed without
> rebooting which is rather time consuming with my setup. There doesn't
> seem to be an obvious way to tell what the "default" is.
[...]
I'm not recommending that you set it. I was concerned that forcing ASPM
on could possibly trigger this problem.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
signature.asc
Description: This is a digitally signed message part
