From: Massimo cetra <ctrix+debianbugs@navynet.it>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org,
"Peter Huang (Peng)" <peter.huangpeng@huawei.com>
Subject: Re: Kernel panic with bridge networking
Date: Thu, 12 Apr 2012 16:57:06 +0200 [thread overview]
Message-ID: <4F86ED42.9030603@navynet.it> (raw)
In-Reply-To: <1334235175.5300.6329.camel@edumazet-glaptop>
On 12/04/2012 14:52, Eric Dumazet wrote:
> On Thu, 2012-04-12 at 14:30 +0200, Massimo Cetra wrote:
>> Hello,
>>
>> i am experiencing a panic whose logs are attached (grabbed with netconsole).
>>
> Known issue, and we are waiting from a fix from Peter.
>
> https://lkml.org/lkml/2012/3/31/17
>
> Peter, any progress on your side ?
>
Thanks Eric,
is there a way to prvent those panics, meanwhile ?
I mean: i don't understand if it depends strictly on IPv6 or it has
other causes.
The same kernel with ipv6 enabled but without ipv6 is not actually
panic-ing ...
And thanks to Peter as well.
Massimo
next prev parent reply other threads:[~2012-04-12 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 12:30 Kernel panic with bridge networking Massimo Cetra
2012-04-12 12:52 ` Eric Dumazet
2012-04-12 14:57 ` Massimo cetra [this message]
2012-04-13 2:45 ` Peter Huang (Peng)
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=4F86ED42.9030603@navynet.it \
--to=ctrix+debianbugs@navynet.it \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peter.huangpeng@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).