* net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
@ 2010-03-23 18:28 Tantilov, Emil S
2010-03-24 6:33 ` David Miller
0 siblings, 1 reply; 17+ messages in thread
From: Tantilov, Emil S @ 2010-03-23 18:28 UTC (permalink / raw)
To: netdev; +Cc: David Miller, Stephen Hemminger
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:
[ 436.118773] ------------[ cut here ]------------
[ 436.124009] WARNING: at net/ipv6/ip6_fib.c:1159 fib6_del+0x44/0x39f()
[ 436.131280] Hardware name: S5520HC
[ 436.135147] Modules linked in: bnx2 e1000e ixgbe mdio e1000
[ 436.141894] Pid: 7290, comm: ethtool Not tainted 2.6.33-net-next-master-bisect #45
[ 436.150427] Call Trace:
[ 436.153230] [<ffffffff81033c41>] ? __wake_up+0x43/0x50
[ 436.159139] [<ffffffff8142728d>] ? fib6_del+0x44/0x39f
[ 436.165043] [<ffffffff81038e97>] warn_slowpath_common+0x77/0x8f
[ 436.171826] [<ffffffff81038ebe>] warn_slowpath_null+0xf/0x11
[ 436.178321] [<ffffffff8142728d>] fib6_del+0x44/0x39f
[ 436.184037] [<ffffffff81424864>] __ip6_del_rt+0x49/0x68
[ 436.190043] [<ffffffff814249d3>] ip6_del_rt+0x38/0x3a
[ 436.195855] [<ffffffff8141fe8f>] __ipv6_ifa_notify+0x141/0x17c
[ 436.202541] [<ffffffff814209bf>] addrconf_ifdown+0x1e2/0x292
[ 436.209034] [<ffffffff8142199a>] addrconf_notify+0x6e7/0x7a0
[ 436.215531] [<ffffffff814addec>] ? _raw_spin_lock_irqsave+0x11/0x19
[ 436.222730] [<ffffffff81045ac6>] ? spin_unlock_irqrestore+0x9/0xb
[ 436.229727] [<ffffffff81046266>] ? del_timer+0x72/0x80
[ 436.235644] [<ffffffff81426914>] ? fib6_age+0x0/0x6e
[ 436.241723] [<ffffffff8103e73d>] ? local_bh_enable_ip+0x9/0xb
[ 436.248639] [<ffffffff814add75>] ? _raw_spin_unlock_bh+0x12/0x14
[ 436.255880] [<ffffffff814271da>] ? fib6_run_gc+0xca/0xcf
[ 436.262297] [<ffffffff814b05c0>] notifier_call_chain+0x33/0x5b
[ 436.283900] [<ffffffff810556c5>] __raw_notifier_call_chain+0x9/0xb
[ 436.291282] [<ffffffff810556d6>] raw_notifier_call_chain+0xf/0x11
[ 436.298624] [<ffffffff813953f9>] call_netdevice_notifiers+0x16/0x18
[ 436.306172] [<ffffffff81395912>] dev_close+0x39/0x3f
[ 436.312204] [<ffffffffa00580dd>] e1000_diag_test+0xc0/0x952 [e1000e]
[ 436.319788] [<ffffffff810d4727>] ? __kmalloc+0x103/0x115
[ 436.326200] [<ffffffff81398703>] ? ethtool_self_test+0x97/0x111
[ 436.333300] [<ffffffff8139871f>] ethtool_self_test+0xb3/0x111
[ 436.340254] [<ffffffff81399928>] dev_ethtool+0x891/0xd3d
[ 436.346721] [<ffffffff813974b2>] dev_ioctl+0x4c2/0x61d
[ 436.352944] [<ffffffff810a42b0>] ? lock_page+0x11/0x29
[ 436.359167] [<ffffffff810a5865>] ? filemap_fault+0x1b4/0x308
[ 436.365973] [<ffffffff810a4391>] ? unlock_page+0xf/0x11
[ 436.372292] [<ffffffff813843e0>] sock_do_ioctl+0x3b/0x46
[ 436.378745] [<ffffffff813845f8>] sock_ioctl+0x20d/0x220
[ 436.385071] [<ffffffff810e6d0b>] vfs_ioctl+0x2a/0x9d
[ 436.391085] [<ffffffff810e7282>] do_vfs_ioctl+0x48c/0x4dd
[ 436.397599] [<ffffffff814b057e>] ? do_page_fault+0x23e/0x24d
[ 436.404466] [<ffffffff810e732a>] sys_ioctl+0x57/0x7a
[ 436.410540] [<ffffffff81002a2b>] system_call_fastpath+0x16/0x1b
[ 436.417694] ---[ end trace c17f3867d68797ab ]---
[ 583.838894] general protection fault: 0000 [#1] SMP
[ 583.844981] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:0b:00.0/local_cpus
[ 583.854839] CPU 10
[ 583.857051] Modules linked in: bnx2 ixgbe mdio e1000 [last unloaded: e1000e]
[ 583.866400]
[ 583.868450] Pid: 7644, comm: ifconfig Tainted: G W 2.6.33-net-next-master-bisect #45 S5520HC/S5520HC
[ 583.880203] RIP: 0010:[<ffffffff81423ac0>] [<ffffffff81423ac0>] fib6_ifdown+0xb/0x26
[ 583.889810] RSP: 0018:ffff8801eb0afbe8 EFLAGS: 00010202
[ 583.896143] RAX: ffff8801ebbac000 RBX: 6b6b6b6b6b6b6b6b RCX: ffffffff81c13c60
[ 583.904517] RDX: ffffffff81c13c60 RSI: ffff8801eb0afd28 RDI: 6b6b6b6b6b6b6b6b
[ 583.912894] RBP: ffff8801eb0afbe8 R08: 0000000000000000 R09: ffff8801ae27d100
[ 583.921324] R10: ffff8801ae27cfc0 R11: ffff8801edaab2c0 R12: ffff8801eb0afc78
[ 583.921327] R13: ffffffff81c13c60 R14: ffff8801eb0afd28 R15: 0000000000000000
[ 583.921331] FS: 00007fa9c7486710(0000) GS:ffff880028340000(0000) knlGS:0000000000000000
[ 583.921334] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 583.921336] CR2: 000000377bcbd268 CR3: 00000001eb9e2000 CR4: 00000000000006e0
[ 583.921339] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 583.921342] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 583.921345] Process ifconfig (pid: 7644, threadinfo ffff8801eb0ae000, task ffff8801ed774bf0)
[ 583.921347] Stack:
[ 583.921348] ffff8801eb0afc28 ffffffff81427621 0000000000000000 ffffffff81c13c60
[ 583.921352] <0> 0000000000000000 ffff8801eb88b1f0 ffff8801eb0afc78 ffff8801ef045c78
[ 583.921355] <0> ffff8801eb0afc48 ffffffff81426cef ffff8801eb0afc48 ffff8801eb0afc78
[ 583.921359] Call Trace:
[ 583.921365] [<ffffffff81427621>] fib6_clean_node+0x39/0xa2
[ 583.921370] [<ffffffff81426cef>] fib6_walk_continue+0xa1/0x101
[ 583.921374] [<ffffffff81426da2>] fib6_walk+0x53/0x6a
[ 583.921378] [<ffffffff81426df3>] fib6_clean_tree+0x3a/0x3c
[ 583.921382] [<ffffffff814275e8>] ? fib6_clean_node+0x0/0xa2
[ 583.921386] [<ffffffff81423ab5>] ? fib6_ifdown+0x0/0x26
[ 583.921390] [<ffffffff81426e67>] fib6_clean_all+0x58/0x76
Emil
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
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
0 siblings, 1 reply; 17+ messages in thread
From: David Miller @ 2010-03-24 6:33 UTC (permalink / raw)
To: emil.s.tantilov; +Cc: netdev, shemminger
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.
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-03-24 6:33 ` David Miller
@ 2010-04-05 23:03 ` Tantilov, Emil S
2010-04-05 23:12 ` David Miller
0 siblings, 1 reply; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-05 23:03 UTC (permalink / raw)
To: shemminger; +Cc: netdev, David Miller
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.
Thanks,
Emil
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-05 23:03 ` Tantilov, Emil S
@ 2010-04-05 23:12 ` David Miller
2010-04-05 23:50 ` Tantilov, Emil S
0 siblings, 1 reply; 17+ messages in thread
From: David Miller @ 2010-04-05 23:12 UTC (permalink / raw)
To: emil.s.tantilov; +Cc: shemminger, netdev
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
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 2:15 ` Stephen Hemminger
0 siblings, 2 replies; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-05 23:50 UTC (permalink / raw)
To: David Miller; +Cc: shemminger, netdev
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:
[ 55.706583] WARNING: at net/ipv6/ip6_fib.c:1170 fib6_del+0x44/0x39f [ipv6]()
[ 55.714851] Hardware name: S5520HC
[ 55.719037] Modules linked in: ipv6 e1000e e1000
[ 55.724866] Pid: 5599, comm: ifconfig Not tainted 2.6.34-rc1-net-next-e1000e-040510 #9
[ 55.734418] Call Trace:
[ 55.737540] [<ffffffff81033a3e>] ? __wake_up+0x43/0x50
[ 55.743773] [<ffffffffa006cb4e>] ? fib6_del+0x44/0x39f [ipv6]
[ 55.750687] [<ffffffff81038b1e>] warn_slowpath_common+0x77/0x8f
[ 55.757793] [<ffffffff81038b45>] warn_slowpath_null+0xf/0x11
[ 55.764608] [<ffffffffa006cb4e>] fib6_del+0x44/0x39f [ipv6]
[ 55.771314] [<ffffffffa006a13b>] __ip6_del_rt+0x49/0x68 [ipv6]
[ 55.778319] [<ffffffffa006a2aa>] ip6_del_rt+0x38/0x3a [ipv6]
[ 55.785136] [<ffffffffa0065573>] __ipv6_ifa_notify+0x141/0x17d [ipv6]
[ 55.792816] [<ffffffffa00660a4>] addrconf_ifdown+0x1ed/0x2cb [ipv6]
[ 55.800300] [<ffffffffa0067126>] addrconf_notify+0x705/0x7b6 [ipv6]
[ 55.807788] [<ffffffff810456ce>] ? spin_unlock_irqrestore+0x9/0xb
[ 55.815088] [<ffffffff81045b80>] ? __mod_timer+0x125/0x137
[ 55.821703] [<ffffffff8144eb60>] ? _raw_write_unlock_bh+0x12/0x14
[ 55.828995] [<ffffffff8103e37d>] ? local_bh_enable_ip+0x9/0xb
[ 55.835906] [<ffffffff8144ec75>] ? _raw_spin_unlock_bh+0x12/0x14
[ 55.843109] [<ffffffffa006ca9b>] ? fib6_run_gc+0xca/0xcf [ipv6]
[ 55.850213] [<ffffffff81451b29>] notifier_call_chain+0x33/0x5b
[ 55.857216] [<ffffffff81055575>] __raw_notifier_call_chain+0x9/0xb
[ 55.864604] [<ffffffff81055586>] raw_notifier_call_chain+0xf/0x11
[ 55.871901] [<ffffffff81397d8f>] call_netdevice_notifiers+0x16/0x18
[ 55.879390] [<ffffffff81397eb2>] __dev_notify_flags+0x35/0x59
[ 55.886293] [<ffffffff81397f1c>] dev_change_flags+0x46/0x52
[ 55.893007] [<ffffffff813f0844>] devinet_ioctl+0x27f/0x54b
[ 55.899614] [<ffffffff813f2c18>] inet_ioctl+0x8a/0xa2
[ 55.905733] [<ffffffff81387275>] sock_do_ioctl+0x26/0x46
[ 55.912149] [<ffffffff81387490>] sock_ioctl+0x1fb/0x20e
[ 55.918461] [<ffffffff810e7b4b>] vfs_ioctl+0x2a/0x9d
[ 55.924495] [<ffffffff810e80c2>] do_vfs_ioctl+0x48c/0x4dd
[ 55.930999] [<ffffffff810e816a>] sys_ioctl+0x57/0x7a
[ 55.937033] [<ffffffff81002a2b>] system_call_fastpath+0x16/0x1b
[ 55.944123] ---[ end trace c1c390412f982fb6 ]---
[ 55.949677] Freeing alive inet6 address ffff8801eee32000
[ 56.034060] fib6_clean_node: del failed: rt=ffff8801ec984e00@(null) err=-2
Emil
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-05 23:50 ` Tantilov, Emil S
@ 2010-04-05 23:53 ` David Miller
2010-04-06 4:39 ` Stephen Hemminger
` (2 more replies)
2010-04-06 2:15 ` Stephen Hemminger
1 sibling, 3 replies; 17+ messages in thread
From: David Miller @ 2010-04-05 23:53 UTC (permalink / raw)
To: emil.s.tantilov; +Cc: shemminger, netdev
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:
Ok, Stephen please look into this, we've had this regression
for almost two weeks now.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-05 23:50 ` Tantilov, Emil S
2010-04-05 23:53 ` David Miller
@ 2010-04-06 2:15 ` Stephen Hemminger
2010-04-06 2:37 ` Tantilov, Emil S
1 sibling, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-06 2:15 UTC (permalink / raw)
To: Tantilov, Emil S; +Cc: David Miller, netdev
On Mon, 5 Apr 2010 17:50:38 -0600
"Tantilov, Emil S" <emil.s.tantilov@intel.com> wrote:
> 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:
>
> [ 55.706583] WARNING: at net/ipv6/ip6_fib.c:1170 fib6_del+0x44/0x39f [ipv6]()
> [ 55.714851] Hardware name: S5520HC
> [ 55.719037] Modules linked in: ipv6 e1000e e1000
> [ 55.724866] Pid: 5599, comm: ifconfig Not tainted 2.6.34-rc1-net-next-e1000e-040510 #9
> [ 55.734418] Call Trace:
> [ 55.737540] [<ffffffff81033a3e>] ? __wake_up+0x43/0x50
> [ 55.743773] [<ffffffffa006cb4e>] ? fib6_del+0x44/0x39f [ipv6]
> [ 55.750687] [<ffffffff81038b1e>] warn_slowpath_common+0x77/0x8f
> [ 55.757793] [<ffffffff81038b45>] warn_slowpath_null+0xf/0x11
> [ 55.764608] [<ffffffffa006cb4e>] fib6_del+0x44/0x39f [ipv6]
> [ 55.771314] [<ffffffffa006a13b>] __ip6_del_rt+0x49/0x68 [ipv6]
> [ 55.778319] [<ffffffffa006a2aa>] ip6_del_rt+0x38/0x3a [ipv6]
> [ 55.785136] [<ffffffffa0065573>] __ipv6_ifa_notify+0x141/0x17d [ipv6]
> [ 55.792816] [<ffffffffa00660a4>] addrconf_ifdown+0x1ed/0x2cb [ipv6]
> [ 55.800300] [<ffffffffa0067126>] addrconf_notify+0x705/0x7b6 [ipv6]
> [ 55.807788] [<ffffffff810456ce>] ? spin_unlock_irqrestore+0x9/0xb
> [ 55.815088] [<ffffffff81045b80>] ? __mod_timer+0x125/0x137
> [ 55.821703] [<ffffffff8144eb60>] ? _raw_write_unlock_bh+0x12/0x14
> [ 55.828995] [<ffffffff8103e37d>] ? local_bh_enable_ip+0x9/0xb
> [ 55.835906] [<ffffffff8144ec75>] ? _raw_spin_unlock_bh+0x12/0x14
> [ 55.843109] [<ffffffffa006ca9b>] ? fib6_run_gc+0xca/0xcf [ipv6]
> [ 55.850213] [<ffffffff81451b29>] notifier_call_chain+0x33/0x5b
> [ 55.857216] [<ffffffff81055575>] __raw_notifier_call_chain+0x9/0xb
> [ 55.864604] [<ffffffff81055586>] raw_notifier_call_chain+0xf/0x11
> [ 55.871901] [<ffffffff81397d8f>] call_netdevice_notifiers+0x16/0x18
> [ 55.879390] [<ffffffff81397eb2>] __dev_notify_flags+0x35/0x59
> [ 55.886293] [<ffffffff81397f1c>] dev_change_flags+0x46/0x52
> [ 55.893007] [<ffffffff813f0844>] devinet_ioctl+0x27f/0x54b
> [ 55.899614] [<ffffffff813f2c18>] inet_ioctl+0x8a/0xa2
> [ 55.905733] [<ffffffff81387275>] sock_do_ioctl+0x26/0x46
> [ 55.912149] [<ffffffff81387490>] sock_ioctl+0x1fb/0x20e
> [ 55.918461] [<ffffffff810e7b4b>] vfs_ioctl+0x2a/0x9d
> [ 55.924495] [<ffffffff810e80c2>] do_vfs_ioctl+0x48c/0x4dd
> [ 55.930999] [<ffffffff810e816a>] sys_ioctl+0x57/0x7a
> [ 55.937033] [<ffffffff81002a2b>] system_call_fastpath+0x16/0x1b
> [ 55.944123] ---[ end trace c1c390412f982fb6 ]---
> [ 55.949677] Freeing alive inet6 address ffff8801eee32000
> [ 56.034060] fib6_clean_node: del failed: rt=ffff8801ec984e00@(null) err=-2
>
Which driver is this, the test function is driver dependent?
--
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-06 2:15 ` Stephen Hemminger
@ 2010-04-06 2:37 ` Tantilov, Emil S
0 siblings, 0 replies; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-06 2:37 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: David Miller, netdev
Stephen Hemminger wrote:
> On Mon, 5 Apr 2010 17:50:38 -0600
> "Tantilov, Emil S" <emil.s.tantilov@intel.com> wrote:
>
>> 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:
>>
>> [ 55.706583] WARNING: at net/ipv6/ip6_fib.c:1170
>> fib6_del+0x44/0x39f [ipv6]() [ 55.714851] Hardware name: S5520HC
>> [ 55.719037] Modules linked in: ipv6 e1000e e1000
>> [ 55.724866] Pid: 5599, comm: ifconfig Not tainted
>> 2.6.34-rc1-net-next-e1000e-040510 #9 [ 55.734418] Call Trace: [
>> 55.737540] [<ffffffff81033a3e>] ? __wake_up+0x43/0x50 [
>> 55.743773] [<ffffffffa006cb4e>] ? fib6_del+0x44/0x39f [ipv6] [
>> 55.750687] [<ffffffff81038b1e>] warn_slowpath_common+0x77/0x8f [
>> 55.757793] [<ffffffff81038b45>] warn_slowpath_null+0xf/0x11 [
>> 55.764608] [<ffffffffa006cb4e>] fib6_del+0x44/0x39f [ipv6] [
>> 55.771314] [<ffffffffa006a13b>] __ip6_del_rt+0x49/0x68 [ipv6] [
>> 55.778319] [<ffffffffa006a2aa>] ip6_del_rt+0x38/0x3a [ipv6] [
>> 55.785136] [<ffffffffa0065573>] __ipv6_ifa_notify+0x141/0x17d
>> [ipv6] [ 55.792816] [<ffffffffa00660a4>]
>> addrconf_ifdown+0x1ed/0x2cb [ipv6] [ 55.800300]
>> [<ffffffffa0067126>] addrconf_notify+0x705/0x7b6 [ipv6] [
>> 55.807788] [<ffffffff810456ce>] ? spin_unlock_irqrestore+0x9/0xb [
>> 55.815088] [<ffffffff81045b80>] ? __mod_timer+0x125/0x137 [
>> 55.821703] [<ffffffff8144eb60>] ? _raw_write_unlock_bh+0x12/0x14 [
>> 55.828995] [<ffffffff8103e37d>] ? local_bh_enable_ip+0x9/0xb [
>> 55.835906] [<ffffffff8144ec75>] ? _raw_spin_unlock_bh+0x12/0x14 [
>> 55.843109] [<ffffffffa006ca9b>] ? fib6_run_gc+0xca/0xcf [ipv6] [
>> 55.850213] [<ffffffff81451b29>] notifier_call_chain+0x33/0x5b [
>> 55.857216] [<ffffffff81055575>] __raw_notifier_call_chain+0x9/0xb [
>> 55.864604] [<ffffffff81055586>] raw_notifier_call_chain+0xf/0x11 [
>> 55.871901] [<ffffffff81397d8f>] call_netdevice_notifiers+0x16/0x18
>> [ 55.879390] [<ffffffff81397eb2>] __dev_notify_flags+0x35/0x59 [
>> 55.886293] [<ffffffff81397f1c>] dev_change_flags+0x46/0x52 [
>> 55.893007] [<ffffffff813f0844>] devinet_ioctl+0x27f/0x54b [
>> 55.899614] [<ffffffff813f2c18>] inet_ioctl+0x8a/0xa2 [ 55.905733]
>> [<ffffffff81387275>] sock_do_ioctl+0x26/0x46 [ 55.912149]
>> [<ffffffff81387490>] sock_ioctl+0x1fb/0x20e [ 55.918461]
>> [<ffffffff810e7b4b>] vfs_ioctl+0x2a/0x9d [ 55.924495]
>> [<ffffffff810e80c2>] do_vfs_ioctl+0x48c/0x4dd [ 55.930999]
>> [<ffffffff810e816a>] sys_ioctl+0x57/0x7a [ 55.937033]
>> [<ffffffff81002a2b>] system_call_fastpath+0x16/0x1b [ 55.944123]
>> ---[ end trace c1c390412f982fb6 ]--- [ 55.949677] Freeing alive
>> inet6 address ffff8801eee32000 [ 56.034060] fib6_clean_node: del
>> failed: rt=ffff8801ec984e00@(null) err=-2
>>
>
> Which driver is this, the test function is driver dependent?
I have seen the panic with e1000e and bnx2.
Emil
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-05 23:53 ` David Miller
@ 2010-04-06 4:39 ` Stephen Hemminger
2010-04-09 0:54 ` Stephen Hemminger
2010-04-09 22:19 ` Stephen Hemminger
2 siblings, 0 replies; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-06 4:39 UTC (permalink / raw)
To: emil.s.tantilov; +Cc: David Miller, netdev
I can not reproduce this with current net-next and e1000e.
Please recheck that you are running the right code.
# ip addr show dev eth3
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:17:c3:a9:fb brd ff:ff:ff:ff:ff:ff
inet6 2001:db8:0:f101::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::215:17ff:fec3:a9fb/64 scope link
valid_lft forever preferred_lft forever
# ip addr show dev eth3
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:17:c3:a9:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.1.12/24 brd 192.168.1.255 scope global eth3
inet6 2001:db8:0:f101::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::215:17ff:fec3:a9fb/64 scope link
valid_lft forever preferred_lft forever
# ethtool -t eth3
The test result is PASS
The test extra info:
Register test (offline) 0
Eeprom test (offline) 0
Interrupt test (offline) 0
Loopback test (offline) 0
Link test (on/offline) 0
No failures, no backtrace, nothing?
$ git log net/ipv6/addrconf.c
commit 4b97efdf392563bf03b4917a0b5add2df65de39a
Author: Patrick McHardy <kaber@trash.net>
Date: Fri Mar 26 20:27:49 2010 -0700
net: fix netlink address dumping in IPv4/IPv6
When a dump is interrupted at the last device in a hash chain and
then continued, "idx" won't get incremented past s_idx, so s_ip_idx
is not reset when moving on to the next device. This means of all
following devices only the last n - s_ip_idx addresses are dumped.
Tested-by: Pawel Staszewski <pstaszewski@itcare.pl>
Signed-off-by: Patrick McHardy <kaber@trash.net>
commit b79d1d54cf0672f764402fe4711ef5306f917bd3
Author: David S. Miller <davem@davemloft.net>
Date: Thu Mar 25 21:39:21 2010 -0700
ipv6: Fix result generation in ipv6_get_ifaddr().
Finishing naturally from hlist_for_each_entry(x, ...) does not result
in 'x' being NULL.
Signed-off-by: David S. Miller <davem@davemloft.net>
commit b54c9b98bbfb4836b1f7441c5a9db24affd3c2e9
Author: David S. Miller <davem@davemloft.net>
Date: Thu Mar 25 21:25:30 2010 -0700
ipv6: Preserve pervious behavior in ipv6_link_dev_addr().
Use list_add_tail() to get the behavior we had before
the list_head conversion for ipv6 address lists.
Signed-off-by: David S. Miller <davem@davemloft.net>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
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 22:19 ` Stephen Hemminger
2 siblings, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-09 0:54 UTC (permalink / raw)
To: David Miller; +Cc: emil.s.tantilov, netdev
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:
>
> Ok, Stephen please look into this, we've had this regression
> for almost two weeks now.
I can't reproduce it, on e1000e.
Since the symptoms match the original problem that you already fixed,
I have to assume that it is fixed but the reporter (Emil) had not
updated his kernel correctly.
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 0:54 ` Stephen Hemminger
@ 2010-04-09 8:19 ` Tantilov, Emil S
2010-04-09 15:07 ` Stephen Hemminger
0 siblings, 1 reply; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-09 8:19 UTC (permalink / raw)
To: Stephen Hemminger, David Miller; +Cc: netdev
Stephen Hemminger wrote:
> 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:
>>
>> Ok, Stephen please look into this, we've had this regression
>> for almost two weeks now.
>
> I can't reproduce it, on e1000e.
> Since the symptoms match the original problem that you already fixed,
> I have to assume that it is fixed but the reporter (Emil) had not
> updated his kernel correctly.
My tree is up to date, but can you point me to the patch that is supposed to fix this?
Thanks,
Emil
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 8:19 ` Tantilov, Emil S
@ 2010-04-09 15:07 ` Stephen Hemminger
2010-04-09 17:50 ` Tantilov, Emil S
0 siblings, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-09 15:07 UTC (permalink / raw)
To: Emil S Tantilov; +Cc: netdev, David Miller
Send me your kernel config. And are you running tests online or offline
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 15:07 ` Stephen Hemminger
@ 2010-04-09 17:50 ` Tantilov, Emil S
2010-04-12 4:49 ` Stephen Hemminger
0 siblings, 1 reply; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-09 17:50 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev, David Miller
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
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
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 12115 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-05 23:53 ` David Miller
2010-04-06 4:39 ` Stephen Hemminger
2010-04-09 0:54 ` Stephen Hemminger
@ 2010-04-09 22:19 ` Stephen Hemminger
2010-04-09 23:00 ` Tantilov, Emil S
2 siblings, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-09 22:19 UTC (permalink / raw)
To: emil.s.tantilov; +Cc: David Miller, netdev
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.
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 22:19 ` Stephen Hemminger
@ 2010-04-09 23:00 ` Tantilov, Emil S
2010-04-10 2:21 ` Stephen Hemminger
0 siblings, 1 reply; 17+ messages in thread
From: Tantilov, Emil S @ 2010-04-09 23:00 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: David Miller, netdev
Stephen Hemminger wrote:
> 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.
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 23:00 ` Tantilov, Emil S
@ 2010-04-10 2:21 ` Stephen Hemminger
0 siblings, 0 replies; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-10 2:21 UTC (permalink / raw)
To: Emil S Tantilov; +Cc: David Miller, netdev
>
> 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
Yes, that causes WARN() to trigger, but only if there is a delay
between ethtool (down/up transition) and the address delete.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
2010-04-09 17:50 ` Tantilov, Emil S
@ 2010-04-12 4:49 ` Stephen Hemminger
0 siblings, 0 replies; 17+ messages in thread
From: Stephen Hemminger @ 2010-04-12 4:49 UTC (permalink / raw)
To: Emil S Tantilov; +Cc: netdev, David Miller
----- "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.
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2010-04-12 4:49 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.