From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Emil S Tantilov <emil.s.tantilov@intel.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
Date: Sun, 11 Apr 2010 21:49:19 -0700 (PDT) [thread overview]
Message-ID: <18279548.81981271047759991.JavaMail.root@tahiti.vyatta.com> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FE4F6B7C4@rrsmsx501.amr.corp.intel.com>
----- "Emil S Tantilov" <emil.s.tantilov@intel.com> wrote:
> Stephen Hemminger wrote:
> > Send me your kernel config. And are you running tests online or
> > offline
>
> Config attached. The kernel runs on top of RHEL5.4, not sure if that
> is significant, but should explain some of the sysfs deprecated
> options enabled in it.
>
> The test is offline (online doesn't do much other than link check).
>
> I also reproduced it with a fresh pull from this morning. Looks like
> it is easier to reproduce after you pass some traffic, just assigning
> IPv6 address may not be enough. Also rmmod hangs.
>
> Thanks,
> Emil
I have a fix, but it needs more testing.
next prev parent reply other threads:[~2010-04-12 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:28 net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6 Tantilov, Emil S
2010-03-24 6:33 ` David Miller
2010-04-05 23:03 ` Tantilov, Emil S
2010-04-05 23:12 ` David Miller
2010-04-05 23:50 ` Tantilov, Emil S
2010-04-05 23:53 ` David Miller
2010-04-06 4:39 ` Stephen Hemminger
2010-04-09 0:54 ` Stephen Hemminger
2010-04-09 8:19 ` Tantilov, Emil S
2010-04-09 15:07 ` Stephen Hemminger
2010-04-09 17:50 ` Tantilov, Emil S
2010-04-12 4:49 ` Stephen Hemminger [this message]
2010-04-09 22:19 ` Stephen Hemminger
2010-04-09 23:00 ` Tantilov, Emil S
2010-04-10 2:21 ` Stephen Hemminger
2010-04-06 2:15 ` Stephen Hemminger
2010-04-06 2:37 ` Tantilov, Emil S
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=18279548.81981271047759991.JavaMail.root@tahiti.vyatta.com \
--to=stephen.hemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=emil.s.tantilov@intel.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).