[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FE4FCD423@rrsmsx501.amr.corp.intel.com>
Date: Fri, 9 Apr 2010 17:00:31 -0600
From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
To: Stephen Hemminger <shemminger@...tta.com>
CC: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic
on interface with IPv6
Stephen Hemminger wrote:
> On Mon, 05 Apr 2010 16:53:17 -0700 (PDT)
> David Miller <davem@...emloft.net> wrote:
>
>> From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
>> Date: Mon, 5 Apr 2010 17:50:38 -0600
>>
>>> David Miller wrote:
>>>> From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
>>>> Date: Mon, 5 Apr 2010 17:03:56 -0600
>>>>
>>>>> David Miller wrote:
>>>>>> From: "Tantilov, Emil S" <emil.s.tantilov@...el.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.
Stock net-next, nothing external.
I played with it some more to get the exact commands. Looks like the following should repro it:
ifconfig eth0 inet6 add fec0::1509/112 up
ethtool -t eth0
ifconfig eth0 inet6 del fec0::1509/112
Thanks,
Emil--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists