Andy Green wrote:
> The obvious guess is WLAN related
> stuff but only because it was around suspend / resume.

Hmm, suspend/resume seems to work fine for me. My environment is of
course very reduced, basically just kernel, udev, sshd, and a shell.

What state was the WLAN in at the time of the resume failure ? Were
all modules loaded (or was this a modular kernel) ? Was there an
association ? On-going traffic ?

- Werner

Reply via email to