From: William Dauchy <william@gandi.net>
To: netdev@vger.kernel.org
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: igbvf warning on 3.14.x
Date: Fri, 15 Aug 2014 15:14:26 +0200 [thread overview]
Message-ID: <20140815131426.GA4638@gandi.net> (raw)
[-- 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 --]
next reply other threads:[~2014-08-15 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 13:14 William Dauchy [this message]
2014-08-15 13:27 ` igbvf warning on 3.14.x 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
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=20140815131426.GA4638@gandi.net \
--to=william@gandi.net \
--cc=jeffrey.t.kirsher@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).