From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Stefan Priebe <s.priebe@profihost.ag>
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: Mon, 21 Nov 2011 14:42:28 -0800 [thread overview]
Message-ID: <4ECAD3D4.4070306@intel.com> (raw)
In-Reply-To: <4ECA936E.8060301@profihost.ag>
On 11/21/2011 10:07 AM, Stefan Priebe wrote:
>> You are going to need to clarify some things since as far as I know we
>> never released a v3.0.8 driver, and the kernel in the bug below is a
>> version 2.6.40.8 which sounds more like a modified and possibly
>> backported Linux kernel since as far as I know Linus never released a
>> 2.6.40 kernel version.
> Sorry that my description was so inaccurate. I'm talking about a
> vanilla v3.0.8 linux kernel. Just renamed to 2.6.40.8.
>
>> In order to be able to assist you we will need some additional
>> information. What Linux distro are your running? Do you have the
>> latest updates from them? Also have you tried running the latest
>> out-of-tree driver we provide at e1000.sf.net in order to verify if the
>> same issue occurs with that driver?
> Linux Distri is Debian Lenny but we're running a self compiled vanilla
> 3.0.X kernel. I haven't tried to use the up2date e1000.sf.net driver
> as 3.0 is a long time supported kernel by greg - so all needed fixes
> should be backported or at least send to stable@ so that greg can have
> a look at them.
>
> Thanks!
>
> Stefan
Stefan,
It would be useful if you could try the latest driver from e1000.sf.net
just to verify if this is a bug in the upstream kernel or if it is also
present in our e1000.sf.net.driver. This way we can figure out if this
is an issue where a patch wasn't pushed into the stable kernel or if it
is an issue that still exists in our latest release.
Also could you provide us with the part number you are currently using.
If you could provide us with the device ID for the part via lspci we can
start narrowing down the root cause for the issue as currently we don't
have any information about what hardware you are experiencing this issue on.
Thanks,
Alex
next prev parent reply other threads:[~2011-11-21 22:42 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 [this message]
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
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=4ECAD3D4.4070306@intel.com \
--to=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=s.priebe@profihost.ag \
--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).