From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: Stable Tree <stable@kernel.org>,
stable@vger.kernel.org, Greg KH <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"Jesse Brandeburg <jesse.brandeburg@intel.com> Bruce Allan"
<bruce.w.allan@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Greg Rose <gregory.v.rose@intel.com>,
PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>,
John Ronciak <john.ronciak@intel.com>
Subject: Re: Kernel v3.0.8 igb driver dies when pulling network cable
Date: Wed, 23 Nov 2011 07:15:40 +0100 [thread overview]
Message-ID: <4ECC8F8C.9030607@profihost.ag> (raw)
In-Reply-To: <4ECC1592.60607@intel.com>
Hi Alex,
> It seems like there might be an issue with something specific to your
> board since I tried reproducing the issue here on an 82576 based adapter
> and the stable 3.0.9 kernel I have and I have not had much success.
but as it is working fine with the up2date igb module - it still was
fixed ;-)
To reproduce try the following (gave me 100% success rate). Configure
eth0 to DHCP, leave eth1 unconfigured.
Boot the system with lan cable plugged into eth1 !!
When the boot has finished switch the LAN cable from eth1 to eth0.
> I'm assuming the device that is failing is eth0. I was wondering if you
> could send me the output of the following three commands so that I can
> do some further work to try and isolate the root cause for this issue:
> ethtool eth0
> ethtool -e eth0
> grep eth0 /proc/interrupts
Will send them as soon i have access to the machine again.
> The issue seems to be that your adapter is not detecting that the cable
> was unplugged. This in turn is leaving stale packets on the Tx ring and
> is what is resulting in the dev_watchdog message you are seeing.
Are you sure? Cause when you look at the dmesg you'll see this:
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
STACKTRACE!
igb 0000:0a:00.0: eth0: Reset adapter
eth0: no IPv6 routers present
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
igb 0000:0a:00.0: eth0: Reset adapter
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
So it happens when the cable is plugged in and NOT when i unplug it.
Stefan
prev parent reply other threads:[~2011-11-23 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 12:26 Kernel v3.0.8 igb driver dies when pulling network cable Stefan Priebe
2011-11-21 17:20 ` Alexander Duyck
2011-11-21 18:07 ` Stefan Priebe
2011-11-21 22:42 ` Alexander Duyck
2011-11-22 9:36 ` Stefan Priebe - Profihost AG
2011-11-22 21:35 ` Alexander Duyck
2011-11-23 6:15 ` Stefan Priebe - Profihost AG [this message]
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=4ECC8F8C.9030607@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=gregkh@suse.de \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=stable@kernel.org \
--cc=stable@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).