Rafael J. Wysocki wrote:

On Monday, 14 of July 2008, James Le Cuirot wrote:

quoted

Hi,

Hi,

quoted

uswsusp works great on my machine except for one thing. I use a TAP
device for QEMU and after resuming from suspend, it doesn't work
anymore until I delete it and recreate it. This is rather annoying
because if I have QEMU open, it means I have to close it before
recreating the interface and then boot Windows up again. I use OpenVPN
to create/delete the interface but I think that's all it does. The rest
is done by the kernel. So I'm guessing something's up with the TUN/TAP
driver or uswsusp itself. I'm using version 0.8. Sorry if this has
already been fixed.

This is a kernel problem, adding kernel-related CCs.

I bet it's flow control related. I've fixed a bug in flow control handling for
persistent devices recently.
btw Does it still happen with >= 2.6.26 ?

I'll play with some test code on my laptop and see if I can reproduce this issue.

Max

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/