From: Stephen Hemminger <shemminger@vyatta.com>
To: emil.s.tantilov@intel.com
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
Date: Fri, 9 Apr 2010 15:19:16 -0700 [thread overview]
Message-ID: <20100409151916.633fc58c@nehalam> (raw)
In-Reply-To: <20100405.165317.89399272.davem@davemloft.net>
On Mon, 05 Apr 2010 16:53:17 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
> Date: Mon, 5 Apr 2010 17:50:38 -0600
>
> > David Miller wrote:
> >> From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
> >> Date: Mon, 5 Apr 2010 17:03:56 -0600
> >>
> >>> David Miller wrote:
> >>>> From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
> >>>> Date: Tue, 23 Mar 2010 12:28:08 -0600
> >>>>
> >>>>> Bisecting points to this patch:
> >>>>> http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commitdiff;h=84e8b803f1e16f3a2b8b80f80a63fa2f2f8a9be6
> >>>>>
> >>>>> And I confirmed that the issue goes away after reverting it.
> >>>>>
> >>>>> Steps to reproduce:
> >>>>> 1. Load the driver and configure IPv6 address.
> >>>>> 2. Run ethtool diag:
> >>>>> ethtool -t eth0
> >>>>>
> >>>>> 3. If this doesn't brake it try again, or just do ifdown/up. Other
> >>>>> operations on the interface will eventually panic the system:
> >>>>
> >>>> Stephen please fix this, thanks.
> >>>
> >>> Just FYI - I still see this issue with latest pull from net-2.6.
> >>
> >> It's net-next-2.6 that introduced the problem and has the follow-on
> >> fixes, not net-2.6
> >
> > Same in net-next:
Are you using the standard e1000e driver from net-next or some other
Intel version. It works fine on my e1000e doing online or offline
tests.
# ethtool -i eth4
driver: e1000e
version: 1.0.2-k2
firmware-version: 5.11-2
bus-info: 0000:03:00.0
Do you have any other suggestions (script or anything), that makes
the problem happen.
next prev parent reply other threads:[~2010-04-09 22:19 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
2010-04-09 22:19 ` Stephen Hemminger [this message]
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=20100409151916.633fc58c@nehalam \
--to=shemminger@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).