* igbvf warning on 3.14.x
@ 2014-08-15 13:14 William Dauchy
2014-08-15 13:27 ` Jeff Kirsher
0 siblings, 1 reply; 6+ messages in thread
From: William Dauchy @ 2014-08-15 13:14 UTC (permalink / raw)
To: netdev; +Cc: Jeff Kirsher
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
Hello,
I'm sometimes getting the following trace on a 3.14.x x86_64
the boot cmdline has igb.max_vfs=2
igbvf 0000:01:10.3: PF still resetting
igbvf 0000:01:10.1: PF still resetting
------------[ cut here ]------------
WARNING: CPU: 11 PID: 1 at
drivers/net/ethernet/intel/igbvf/netdev.c:1718 igbvf_close+0x66/0x70()
CPU: 11 PID: 1 Comm: swapper/0 Not tainted 3.14.17 #1
Hardware name: Dell C6100 /0D61XP, BIOS 1.69 06/22/2012
0000000000000009 ffffffffa95a5d15 0000000000000000 ffffffffa90954e8
ffff880c1d33e000 ffff880c1d33e7c0 8000000000000000 0000000000000001
0000000000000001 ffffffffa93a6676 ffff880c1d33e000 ffffc9000624bdb8
Call Trace:
[<ffffffffa95a5d15>] ? dump_stack+0x49/0x7c
[<ffffffffa90954e8>] ? warn_slowpath_common+0x68/0x80
[<ffffffffa93a6676>] ? igbvf_close+0x66/0x70
[<ffffffffa946d878>] ? __dev_close_many+0x88/0xe0
[<ffffffffa946d9f5>] ? __dev_close+0x25/0x40
[<ffffffffa947440b>] ? __dev_change_flags+0xab/0x180
[<ffffffffa94744fe>] ? dev_change_flags+0x1e/0x60
[<ffffffffa9c401fb>] ? ic_close_devs+0x2c/0x40
[<ffffffffa9c41946>] ? ip_auto_config+0xbf3/0xec7
[<ffffffffa9273890>] ? kset_register+0x50/0x70
[<ffffffffa909a2fe>] ? __insert_resource+0x1e/0x130
[<ffffffffa9c40d53>] ? root_nfs_parse_addr+0xa7/0xa7
[<ffffffffa9c10ee5>] ? do_one_initcall+0x8c/0x107
[<ffffffffa9c110ba>] ? kernel_init_freeable+0x15a/0x1e1
[<ffffffffa9c10857>] ? do_early_param+0x9b/0x9b
[<ffffffffa959e9f0>] ? rest_init+0x80/0x80
[<ffffffffa959e9f5>] ? kernel_init+0x5/0xf0
[<ffffffffa95ac764>] ? ret_from_fork+0x74/0xa0
[<ffffffffa959e9f0>] ? rest_init+0x80/0x80
---[ end trace 90b2a2646f143695 ]---
igbvf 0000:01:10.1: PF still resetting
igbvf 0000:01:10.3: PF still resetting
ixgbe 0000:03:00.0: removed PHC on eth6
ixgbe 0000:03:00.1: removed PHC on eth7
What can I do to help debug this trace? Or should I consider this a
normal case?
Regards,
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: igbvf warning on 3.14.x
2014-08-15 13:14 igbvf warning on 3.14.x William Dauchy
@ 2014-08-15 13:27 ` Jeff Kirsher
2014-08-26 7:36 ` William Dauchy
0 siblings, 1 reply; 6+ messages in thread
From: Jeff Kirsher @ 2014-08-15 13:27 UTC (permalink / raw)
To: William Dauchy, Carolyn Wyborny, mitch.a.williams; +Cc: netdev, e1000-devel
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
On Fri, 2014-08-15 at 15:14 +0200, William Dauchy wrote:
> Hello,
>
> I'm sometimes getting the following trace on a 3.14.x x86_64
> the boot cmdline has igb.max_vfs=2
>
> igbvf 0000:01:10.3: PF still resetting
> igbvf 0000:01:10.1: PF still resetting
> ------------[ cut here ]------------
> WARNING: CPU: 11 PID: 1 at
> drivers/net/ethernet/intel/igbvf/netdev.c:1718 igbvf_close+0x66/0x70()
> CPU: 11 PID: 1 Comm: swapper/0 Not tainted 3.14.17 #1
> Hardware name: Dell C6100 /0D61XP, BIOS 1.69 06/22/2012
> 0000000000000009 ffffffffa95a5d15 0000000000000000 ffffffffa90954e8
> ffff880c1d33e000 ffff880c1d33e7c0 8000000000000000 0000000000000001
> 0000000000000001 ffffffffa93a6676 ffff880c1d33e000 ffffc9000624bdb8
> Call Trace:
> [<ffffffffa95a5d15>] ? dump_stack+0x49/0x7c
> [<ffffffffa90954e8>] ? warn_slowpath_common+0x68/0x80
> [<ffffffffa93a6676>] ? igbvf_close+0x66/0x70
> [<ffffffffa946d878>] ? __dev_close_many+0x88/0xe0
> [<ffffffffa946d9f5>] ? __dev_close+0x25/0x40
> [<ffffffffa947440b>] ? __dev_change_flags+0xab/0x180
> [<ffffffffa94744fe>] ? dev_change_flags+0x1e/0x60
> [<ffffffffa9c401fb>] ? ic_close_devs+0x2c/0x40
> [<ffffffffa9c41946>] ? ip_auto_config+0xbf3/0xec7
> [<ffffffffa9273890>] ? kset_register+0x50/0x70
> [<ffffffffa909a2fe>] ? __insert_resource+0x1e/0x130
> [<ffffffffa9c40d53>] ? root_nfs_parse_addr+0xa7/0xa7
> [<ffffffffa9c10ee5>] ? do_one_initcall+0x8c/0x107
> [<ffffffffa9c110ba>] ? kernel_init_freeable+0x15a/0x1e1
> [<ffffffffa9c10857>] ? do_early_param+0x9b/0x9b
> [<ffffffffa959e9f0>] ? rest_init+0x80/0x80
> [<ffffffffa959e9f5>] ? kernel_init+0x5/0xf0
> [<ffffffffa95ac764>] ? ret_from_fork+0x74/0xa0
> [<ffffffffa959e9f0>] ? rest_init+0x80/0x80
> ---[ end trace 90b2a2646f143695 ]---
> igbvf 0000:01:10.1: PF still resetting
> igbvf 0000:01:10.3: PF still resetting
> ixgbe 0000:03:00.0: removed PHC on eth6
> ixgbe 0000:03:00.1: removed PHC on eth7
>
>
> What can I do to help debug this trace? Or should I consider this a
> normal case?
Adding Carolyn (igb maintainer) and e1000-devel mailing list...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: igbvf warning on 3.14.x
2014-08-15 13:27 ` Jeff Kirsher
@ 2014-08-26 7:36 ` William Dauchy
2014-08-26 15:17 ` Wyborny, Carolyn
0 siblings, 1 reply; 6+ messages in thread
From: William Dauchy @ 2014-08-26 7:36 UTC (permalink / raw)
To: Carolyn Wyborny, mitch.a.williams
Cc: William Dauchy, netdev, e1000-devel, Jeff Kirsher
[-- Attachment #1: Type: text/plain, Size: 186 bytes --]
Hi,
On Aug15 06:27, Jeff Kirsher wrote:
> Adding Carolyn (igb maintainer) and e1000-devel mailing list...
any chance to get some feedback on this trace?
Thanks,
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: igbvf warning on 3.14.x
2014-08-26 7:36 ` William Dauchy
@ 2014-08-26 15:17 ` Wyborny, Carolyn
2014-08-26 15:25 ` Fujinaka, Todd
0 siblings, 1 reply; 6+ messages in thread
From: Wyborny, Carolyn @ 2014-08-26 15:17 UTC (permalink / raw)
To: William Dauchy, Williams, Mitch A, Fujinaka, Todd
Cc: netdev@vger.kernel.org, e1000-devel, Kirsher, Jeffrey T
Adding Todd Fujinaka, who is customer support for igbvf. I'll assist if need be.
Thanks,
Carolyn
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of William Dauchy
> Sent: Tuesday, August 26, 2014 12:36 AM
> To: Wyborny, Carolyn; Williams, Mitch A
> Cc: William Dauchy; netdev@vger.kernel.org; e1000-devel; Kirsher, Jeffrey T
> Subject: Re: igbvf warning on 3.14.x
>
> Hi,
>
> On Aug15 06:27, Jeff Kirsher wrote:
> > Adding Carolyn (igb maintainer) and e1000-devel mailing list...
>
> any chance to get some feedback on this trace?
>
> Thanks,
> --
> William
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: igbvf warning on 3.14.x
2014-08-26 15:17 ` Wyborny, Carolyn
@ 2014-08-26 15:25 ` Fujinaka, Todd
2014-08-26 15:54 ` William Dauchy
0 siblings, 1 reply; 6+ messages in thread
From: Fujinaka, Todd @ 2014-08-26 15:25 UTC (permalink / raw)
To: Wyborny, Carolyn, William Dauchy, Williams, Mitch A
Cc: netdev@vger.kernel.org, e1000-devel, Kirsher, Jeffrey T
Sorry, I forgot about this one. And trimming replies on e1000-devel isn't going to help much because we're forced to use outlook here and the threading is abysmal.
Can you please send clear repro steps and I'll submit it to our lab for repro. We'll need what equipment you're running (on both sides of the link), the kind of traffic you're running, the OS & kernel you're running, etc. It might be easier to file a bug on sourceforge if you're able to do that.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujinaka@intel.com
(503) 712-4565
-----Original Message-----
From: Wyborny, Carolyn
Sent: Tuesday, August 26, 2014 8:18 AM
To: William Dauchy; Williams, Mitch A; Fujinaka, Todd
Cc: netdev@vger.kernel.org; e1000-devel; Kirsher, Jeffrey T
Subject: RE: igbvf warning on 3.14.x
Adding Todd Fujinaka, who is customer support for igbvf. I'll assist if need be.
Thanks,
Carolyn
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of William Dauchy
> Sent: Tuesday, August 26, 2014 12:36 AM
> To: Wyborny, Carolyn; Williams, Mitch A
> Cc: William Dauchy; netdev@vger.kernel.org; e1000-devel; Kirsher, Jeffrey T
> Subject: Re: igbvf warning on 3.14.x
>
> Hi,
>
> On Aug15 06:27, Jeff Kirsher wrote:
> > Adding Carolyn (igb maintainer) and e1000-devel mailing list...
>
> any chance to get some feedback on this trace?
>
> Thanks,
> --
> William
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: igbvf warning on 3.14.x
2014-08-26 15:25 ` Fujinaka, Todd
@ 2014-08-26 15:54 ` William Dauchy
0 siblings, 0 replies; 6+ messages in thread
From: William Dauchy @ 2014-08-26 15:54 UTC (permalink / raw)
To: Fujinaka, Todd
Cc: Wyborny, Carolyn, William Dauchy, Williams, Mitch A,
netdev@vger.kernel.org, e1000-devel, Kirsher, Jeffrey T
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
On Aug26 15:25, Fujinaka, Todd wrote:
> Can you please send clear repro steps and I'll submit it to our lab for repro. We'll need what equipment you're running (on both sides of the link), the kind of traffic you're running, the OS & kernel you're running, etc.
the switch used is a cisco C6506
the server is a dell C6100
the network card intel 82576 Gigabit Network Connection
I'm using a linux stable release v3.14.x (last version)
the boot cmdline has igb.max_vfs=2 as argument
no specific traffic but the machine is booting through pxe boot using
nfs
the trace is a bit random at boot time (some boot are clean)
here is a the trace as a reminder:
igbvf 0000:01:10.3: PF still resetting
igbvf 0000:01:10.1: PF still resetting
------------[ cut here ]------------
WARNING: CPU: 11 PID: 1 at
drivers/net/ethernet/intel/igbvf/netdev.c:1718 igbvf_close+0x66/0x70()
CPU: 11 PID: 1 Comm: swapper/0 Not tainted 3.14.17 #1
Hardware name: Dell C6100 /0D61XP, BIOS 1.69 06/22/2012
0000000000000009 ffffffffa95a5d15 0000000000000000 ffffffffa90954e8
ffff880c1d33e000 ffff880c1d33e7c0 8000000000000000 0000000000000001
0000000000000001 ffffffffa93a6676 ffff880c1d33e000 ffffc9000624bdb8
Call Trace:
[<ffffffffa95a5d15>] ? dump_stack+0x49/0x7c
[<ffffffffa90954e8>] ? warn_slowpath_common+0x68/0x80
[<ffffffffa93a6676>] ? igbvf_close+0x66/0x70
[<ffffffffa946d878>] ? __dev_close_many+0x88/0xe0
[<ffffffffa946d9f5>] ? __dev_close+0x25/0x40
[<ffffffffa947440b>] ? __dev_change_flags+0xab/0x180
[<ffffffffa94744fe>] ? dev_change_flags+0x1e/0x60
[<ffffffffa9c401fb>] ? ic_close_devs+0x2c/0x40
[<ffffffffa9c41946>] ? ip_auto_config+0xbf3/0xec7
[<ffffffffa9273890>] ? kset_register+0x50/0x70
[<ffffffffa909a2fe>] ? __insert_resource+0x1e/0x130
[<ffffffffa9c40d53>] ? root_nfs_parse_addr+0xa7/0xa7
[<ffffffffa9c10ee5>] ? do_one_initcall+0x8c/0x107
[<ffffffffa9c110ba>] ? kernel_init_freeable+0x15a/0x1e1
[<ffffffffa9c10857>] ? do_early_param+0x9b/0x9b
[<ffffffffa959e9f0>] ? rest_init+0x80/0x80
[<ffffffffa959e9f5>] ? kernel_init+0x5/0xf0
[<ffffffffa95ac764>] ? ret_from_fork+0x74/0xa0
[<ffffffffa959e9f0>] ? rest_init+0x80/0x80
---[ end trace 90b2a2646f143695 ]---
igbvf 0000:01:10.1: PF still resetting
igbvf 0000:01:10.3: PF still resetting
ixgbe 0000:03:00.0: removed PHC on eth6
ixgbe 0000:03:00.1: removed PHC on eth7
Regards,
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-08-26 15:54 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-15 13:14 igbvf warning on 3.14.x William Dauchy
2014-08-15 13:27 ` Jeff Kirsher
2014-08-26 7:36 ` William Dauchy
2014-08-26 15:17 ` Wyborny, Carolyn
2014-08-26 15:25 ` Fujinaka, Todd
2014-08-26 15:54 ` William Dauchy
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).