netdev - Re: igbvf warning on 3.14.x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1408109225.2391.30.camel@jtkirshe-mobl>
Date:	Fri, 15 Aug 2014 06:27:05 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	William Dauchy <william@...di.net>,
	Carolyn Wyborny <carolyn.wyborny@...el.com>,
	"mitch.a.williams" <mitch.a.williams@...el.com>
Cc:	netdev@...r.kernel.org,
	e1000-devel <e1000-devel@...ts.sourceforge.net>
Subject: Re: igbvf warning on 3.14.x

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...

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)