From: "Peter Huang (Peng)" <peter.huangpeng@huawei.com>
To: 'Eric Dumazet' <eric.dumazet@gmail.com>,
'Massimo Cetra' <ctrix+debianbugs@navynet.it>
Cc: netdev@vger.kernel.org
Subject: Re: Kernel panic with bridge networking
Date: Fri, 13 Apr 2012 10:45:39 +0800 [thread overview]
Message-ID: <004301cd191f$83145200$893cf600$%huangpeng@huawei.com> (raw)
In-Reply-To: <1334235175.5300.6329.camel@edumazet-glaptop>
Hi, Eric
Sorry for delayed reply.
I will send the patch out until tomorrow .
--------------------------------
Peter Huang(peng)
> 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).
> >
> > They look quite similar to what has been described here
> > http://www.spinics.net/lists/linux-net/msg17689.html
> >
> > The patch proposed as the solution (commit
> > 6b1e960fdbd75dcd9bcc3ba5ff8898ff1ad30b6e) seems to be applied (even with
> > small differences) but the problem persists.
> >
> > The kernel is a debian linux-image-3.2.0-2-amd64 version 3.2.12-1
> >
> > Any hint ?
> > I have checked the changelog of 3.2.13 and 3.2.14 and it doesn't seems
> > to be any commit regarding such problems.
> >
> > Massimo Cetra
> >
> > P.S.1: Please CC me as i'm not subscribed.
> > P.S.2: this bug has been submitted to debian as well
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668511
> >
>
> 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
prev parent reply other threads:[~2012-04-13 2:45 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
2012-04-13 2:45 ` Peter Huang (Peng) [this message]
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='004301cd191f$83145200$893cf600$%huangpeng@huawei.com' \
--to=peter.huangpeng@huawei.com \
--cc=ctrix+debianbugs@navynet.it \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).