Re: [Bugme-new] [Bug 13097] New: Kernel will freeze network after using a tun/tap device

Re: [Bugme-new] [Bug 13097] New: Kernel will freeze network after using a tun/tap device

[Andrew Morton]

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

Big fat regression!

On Wed, 15 Apr 2009 22:19:06 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=13097
> 
>            Summary: Kernel will freeze network after using a tun/tap
>                     device
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.30-rc2
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: fragabr@gmail.com
>         Regression: Yes
> 
> 
> I choose the forcedeth driver to report this bug because I think it's related
> to forcedeth and not tun/tap driver, although I can be wrong.
> 
> With 2.6.29 kernel everything works fine, but with 2.6.30-rc2, a simple ping to
> a tun/tap device (for example ping to a vpn using openvpn) will freeze the
> network. In X I can't even use the keyboard anymore.
> 
> It just happens with a tun/tap device, not with a normal ethernet device or a
> normal internet connection.
> 
> If you think it's a tun/tap driver problem, please change the bug, but as I'm
> not completely sure, I choose forcedeth.

An obvious question would be: are you able to test the same setup with
a different type of network card?

Re: [Bugme-new] [Bug 13097] New: Kernel will freeze network after using a tun/tap device

[Herbert Xu]

Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> With 2.6.29 kernel everything works fine, but with 2.6.30-rc2, a simple ping to
>> a tun/tap device (for example ping to a vpn using openvpn) will freeze the
>> network. In X I can't even use the keyboard anymore.
>> 
>> It just happens with a tun/tap device, not with a normal ethernet device or a
>> normal internet connection.
>> 
>> If you think it's a tun/tap driver problem, please change the bug, but as I'm
>> not completely sure, I choose forcedeth.
> 
> An obvious question would be: are you able to test the same setup with
> a different type of network card?

Please get a stack backtrace of all processes on the machine after
the hang, e.g., with Ctrl-ScrollLock.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt