Sander van Grieken sander at
Wed Jan 7 15:07:56 CET 2009

On Wednesday 07 January 2009 14:46:34 Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wednesday 07 January 2009 14:27:57 Andy Green wrote:
> |> | It's not the firmware. It started after I switched to 2.6.28 and the
> |>
> |> newer
> |>
> |> | frameworkd.
> |>
> |> Fair enough, maybe Werner's module param can help.
> |
> | Not an option really. It would only drain the battery more I think?
> |
> | It's also a fix for a symptom, not the root cause.
> Are you sure?  

Yes I'm sure. 

I just brought down the eth0 interface completely (so not only disassociated 
from the AP, but really ifconfig eth0 down). Then I suspend/resume. After 
resume it is up, associated to the AP.

> The S3C MMC driver deactivates the device during suspend, so the
> interface is removed and then re-created. Whether it's configured
> in any way after that depends on user space.

Exactly my point. Something in userspace is bringing it up when it should be 
down, and bringing it down when it should be up.


More information about the devel mailing list