From: "Skidmore, Donald C" <donald.c.skidmore@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: ixgbe: RTNL assertion failed
Date: Fri, 3 May 2013 23:17:39 +0000 [thread overview]
Message-ID: <F6FB0E698C9B3143BDF729DF222866464C28E112@ORSMSX110.amr.corp.intel.com> (raw)
In-Reply-To: <20130503120907.4f13d41b@nehalam.linuxnetplumber.net>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-
> owner@vger.kernel.org] On Behalf Of Stephen Hemminger
> Sent: Friday, May 03, 2013 12:09 PM
> To: Kirsher, Jeffrey T
> Cc: netdev@vger.kernel.org
> Subject: ixgbe: RTNL assertion failed
>
> Running 3.9 kernel, ixgbe is splatting on resume from suspend.
>
> [26430.213254] ixgbe 0000:01:00.0: setting latency timer to 64 [26430.213257]
> RTNL: assertion failed at /build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-
> 3.2.41/net/core/dev.c (1758) [26430.213259] Pid: 7839, comm: kworker/u:1
> Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 [26430.213261] Call Trace:
> [26430.213266] [<ffffffff8128b89e>] ?
> netif_set_real_num_tx_queues+0x5c/0x15e
> [26430.213286] [<ffffffffa0051749>] ? ixgbe_set_num_queues+0x208/0x221
> [ixgbe] [26430.213287] sd 0:0:0:0: [sda] Starting disk [26430.213292]
> [<ffffffffa0054949>] ? ixgbe_init_interrupt_scheme+0x16/0x790 [ixgbe]
> [26430.213299] [<ffffffffa0055aae>] ? ixgbe_resume+0x7a/0xe3 [ixgbe]
> [26430.213303] [<ffffffff81255b7c>] ? pm_op+0xa1/0x141 [26430.213305]
> [<ffffffff81255f40>] ? device_resume+0xa2/0xfc [26430.213307]
> [<ffffffff81255fae>] ? async_resume+0x14/0x38 [26430.213311]
> [<ffffffff810648c4>] ? async_run_entry_fn+0x96/0x142 [26430.213313]
> [<ffffffff8105b225>] ? process_one_work+0x161/0x264 [26430.213316]
> [<ffffffff8105c1e6>] ? worker_thread+0xc2/0x145 [26430.213318]
> [<ffffffff8105c124>] ? manage_workers.isra.25+0x15b/0x15b
> [26430.213320] [<ffffffff8105f321>] ? kthread+0x76/0x7e [26430.213323]
> [<ffffffff81354ab4>] ? kernel_thread_helper+0x4/0x10 [26430.213325]
> [<ffffffff8105f2ab>] ? kthread_worker_fn+0x139/0x139 [26430.213327]
> [<ffffffff81354ab0>] ? gs_change+0x13/0x13
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in the body
> of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
Hey Stephen,
I'm having a little problem finding a path were we call netif_set_real_num_tx_queues without holding RTNL in net-next. While looking over the stack dump one of our engineers noticed the text "Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 ". Could this mean I'm looking over the wrong source? It would make me feel better as I'm not seeing anything as is. :)
Thanks,
-Don Skidmore <donald.c.skidmore@intel.com>
next prev parent reply other threads:[~2013-05-03 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 19:09 ixgbe: RTNL assertion failed Stephen Hemminger
2013-05-03 23:17 ` Skidmore, Donald C [this message]
2013-05-04 1:54 ` Ben Hutchings
2013-05-04 3:51 ` Stephen Hemminger
2013-05-04 21:05 ` Skidmore, Donald C
2013-05-04 21:21 ` Ben Hutchings
2013-05-06 14:58 ` Stephen Hemminger
2013-05-10 4:36 ` Ben Hutchings
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=F6FB0E698C9B3143BDF729DF222866464C28E112@ORSMSX110.amr.corp.intel.com \
--to=donald.c.skidmore@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 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.