netdev - Re: Kernel crash after using new Intel NIC (igb)

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: <201104271346.34431.maxi@daemonizer.de>
Date:	Wed, 27 Apr 2011 13:46:30 +0200
From:	Maximilian Engelhardt <maxi@...monizer.de>
To:	"Wyborny, Carolyn" <carolyn.wyborny@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	StuStaNet Vorstand <vorstand@...sta.mhn.de>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: Re: Kernel crash after using new Intel NIC (igb)

On Wednesday 27 April 2011 01:34:09 Wyborny, Carolyn wrote:
> >-----Original Message-----
> >From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> >On Behalf Of Maximilian Engelhardt
> >Sent: Sunday, April 24, 2011 3:33 PM
> >To: linux-kernel@...r.kernel.org
> >Cc: netdev@...r.kernel.org; StuStaNet Vorstand
> >Subject: Kernel crash after using new Intel NIC (igb)
> >
> >Hello,
> >
> >some time ago we switched some of our servers to a new networking card
> >that
> >uses the Intel igb driver. Since that time we see regular kernel
> >crashes.
> >The crashes happen at very irregular intervals, sometimes after a week
> >uptime,
> >sometimes after a month or even more. They seem to be independent of the
> >server load as they also happen in the night when there is low traffic.
> >
> >The affected server is used as a NAT device with some iptables rules and
> >serves
> >about 2000 people.
> >
> >Attached are two logs of the crashes as well as the output of dmesg,
> >lspci,
> >and /proc/interrupts as well as the used kernel config.
> >
> >I have no idea what might be wrong but I think it is a kernel bug.
> >Perhaps
> >someone with more knowledge has a clue.
> >
> >If needed I can provide additional information or build different
> >kernels.
> >
> >Greetings,
> >Maxi
> 
> Hello,
> 
> I'm sorry you're having crashes since installing our NIC.  Thank you for
> the data.  I haven't had a chance to review it carefully yet, but it looks
> to me like the crashes have us in the stack sometimes and sometimes not. 
> I need to do a bit more research and will need some more information.  Can
> I get an ethtool -i eth# for the device and also lspci -vvv for the
> platform its installed on.
> 
> If you open an issue at SourceForge we will have a place to keep the logs.
> 
> I will research this a bit more and get back to you tomorrow my time.
> 
> Thanks,
> 
> Carolyn
> Carolyn Wyborny
> Linux Development
> LAN Access Division
> Intel Corporation


Hello Carolyn,

Thanks for your response.

I have opened a issue at
https://sourceforge.net/tracker/?func=detail&aid=3293703&group_id=42302&atid=447449
and also posted all information there.


Please not that yesterday I updated the kernel, so I'm now running 2.6.38.4.
Eric Dumazet mentioned on the LKML that this might be a memory corruption that 
my be solved with kernel 2.6.38.

I'll report if the crash happens again, but it might take some times as in the 
past it happened within the interval of weeks to month.


Here is the output of ethtool (with the new 2.6.38.4 kernel):
$ /sbin/ethtool -i eth0
driver: igb
version: 2.1.0-k2
firmware-version: 1.2-1
bus-info: 0000:05:00.0
$ /sbin/ethtool -i eth1
driver: igb
version: 2.1.0-k2
firmware-version: 1.2-1
bus-info: 0000:05:00.1

The output of lspci -vvv is attached (also with kernel 2.6.38.4 but I guess it 
doesn't make any difference)


Greetings,
Maxi

View attachment "lspci_vvv" of type "text/plain" (17016 bytes)

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