From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: James Le Cuirot <chewi@aura-online.co.uk>
Subject: Re: [Suspend-devel] TAP (and TUN?) devices not working after resume
Date: Mon, 14 Jul 2008 18:12:44 +0200
User-Agent: KMail/1.9.6 (enterprise 20070904.708012)
Cc: suspend-devel@lists.sourceforge.net, LKML <linux-kernel@vger.kernel.org>,
       pm list <linux-pm@lists.linux-foundation.org>, netdev@vger.kernel.org
References: <20080714154720.791f6640@symphony>
In-Reply-To: <20080714154720.791f6640@symphony>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200807141812.45264.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 961
Lines: 24

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.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/