From: Max Krasnyansky <maxk@qualcomm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: James Le Cuirot <chewi@aura-online.co.uk>,
suspend-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [Suspend-devel] TAP (and TUN?) devices not working after resume
Date: Thu, 24 Jul 2008 20:50:32 -0700 [thread overview]
Message-ID: <48894D88.9010104@qualcomm.com> (raw)
In-Reply-To: <200807141812.45264.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Monday, 14 of July 2008, James Le Cuirot wrote:
>> Hi,
>
> Hi,
>
>> 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
WARNING: multiple messages have this Message-ID (diff)
From: Max Krasnyansky <maxk@qualcomm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: suspend-devel@lists.sourceforge.net, netdev@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: TAP (and TUN?) devices not working after resume
Date: Thu, 24 Jul 2008 20:50:32 -0700 [thread overview]
Message-ID: <48894D88.9010104@qualcomm.com> (raw)
In-Reply-To: <200807141812.45264.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Monday, 14 of July 2008, James Le Cuirot wrote:
>> Hi,
>
> Hi,
>
>> 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=/
next prev parent reply other threads:[~2008-07-25 3:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080714154720.791f6640@symphony>
2008-07-14 16:12 ` [Suspend-devel] TAP (and TUN?) devices not working after resume Rafael J. Wysocki
2008-07-14 16:31 ` Ray Lee
2008-07-14 16:31 ` Ray Lee
2008-07-14 16:31 ` [Suspend-devel] " Ray Lee
2008-07-25 3:50 ` Max Krasnyansky [this message]
2008-07-25 3:50 ` Max Krasnyansky
2008-11-29 10:18 ` [Suspend-devel] " James Le Cuirot
2008-11-29 10:18 ` James Le Cuirot
2008-07-25 3:50 ` Max Krasnyansky
2008-07-14 16:12 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48894D88.9010104@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=chewi@aura-online.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=suspend-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.