linux-kernel - Re: Kernel v3.0.8 igb driver dies when pulling network cable

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: <4ECAD3D4.4070306@intel.com>
Date:	Mon, 21 Nov 2011 14:42:28 -0800
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	Stefan Priebe <s.priebe@...fihost.ag>
CC:	Stable Tree <stable@...nel.org>, stable@...r.kernel.org,
	Greg KH <gregkh@...e.de>, LKML <linux-kernel@...r.kernel.org>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	"Jesse Brandeburg <jesse.brandeburg@...el.com> Bruce Allan" 
	<bruce.w.allan@...el.com>,
	Carolyn Wyborny <carolyn.wyborny@...el.com>,
	Don Skidmore <donald.c.skidmore@...el.com>,
	Greg Rose <gregory.v.rose@...el.com>,
	PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>,
	John Ronciak <john.ronciak@...el.com>
Subject: Re: Kernel v3.0.8 igb driver dies when pulling network cable

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/