[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1303905858.3166.41.camel@edumazet-laptop>
Date: Wed, 27 Apr 2011 14:04:18 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Maximilian Engelhardt <maxi@...monizer.de>
Cc: "Wyborny, Carolyn" <carolyn.wyborny@...el.com>,
"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)
Le mercredi 27 avril 2011 à 13:46 +0200, Maximilian Engelhardt a écrit :
> 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.
>
Hmm, I suggested to use slub_nomerge to make sure inetpeer kmemcache is
not shared with another (possibly mem corruptor) layer.
Please note we were not able to track the bug in 2.6.37 kernels.
> 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.
>
Thanks
--
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/
Powered by blists - more mailing lists