[ltp] (fwd): Help for those who got their e1000 corrupted

Henrique de Moraes Holschuh linux-thinkpad@linux-thinkpad.org
Fri, 17 Oct 2008 13:31:30 -0300


--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Since it DOES apply to some ThinkPads, and ThinkPad users are the sort of
crowd who do run -rc kernels...

The MAC is written in a label somewhere in the ThinkPad.

The NVM copy and PCI ID information you can ask here from someone that has
the same ThinkPad (remember: you have to supply also the full model number,
and you should use an NVM from the closest machine you can.  Don't use one
from the X60s on the X60, or one from an old-model T60 with the new-model
T60...).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

--5mCyUwZo2JvN/JJP
Content-Type: message/rfc822
Content-Disposition: inline

X-Original-To: hmh@khazad-dum.debian.net
Delivered-To: hmh@khazad-dum.debian.net
Received: from localhost (localhost [127.0.0.1])
	by localhost.khazad-dum.debian.net (Postfix) with ESMTP id 0D77328078
	for <hmh@khazad-dum.debian.net>; Fri, 17 Oct 2008 11:04:11 -0300 (BRT)
X-Virus-Scanned: Debian amavisd-new at khazad-dum.debian.net
Received: from khazad-dum.debian.net ([127.0.0.1])
	by localhost (khazad-dum.debian.net [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id j8BIxrt2+vFT for <hmh@khazad-dum.debian.net>;
	Fri, 17 Oct 2008 11:04:09 -0300 (BRT)
Received: by khazad-dum.debian.net (Postfix, from userid 1000)
	id 5E5E22820D; Fri, 17 Oct 2008 11:04:09 -0300 (BRT)
Received: from mail.messagingengine.com (66.111.4.52) by
  khazad-dum.debian.net with IMAP4-SSL; 17 Oct 2008 14:04:09 -0000
Received: from compute1.internal (compute1.internal [10.202.2.41])
	 by store45m.internal (Cyrus v2.3.12-fmsvn16392) with LMTPA;
	 Fri, 17 Oct 2008 09:59:28 -0400
X-Sieve: CMU Sieve 2.3
X-Spam-source: IP='209.132.176.167', Host='vger.kernel.org', Country='US',
  FromHeader='de', MailFrom='org'
X-Spam-charsets: plain='us-ascii'
X-Delivered-to: hmh@hmh.eng.br
Received: from mx3.messagingengine.com ([10.202.2.202])
  by compute1.internal (LMTPProxy); Fri, 17 Oct 2008 09:59:28 -0400
Received: from vger.kernel.org (vger.kernel.org [209.132.176.167])
	by mx3.messagingengine.com (Postfix) with ESMTP id 277E31A3149
	for <hmh@hmh.eng.br>; Fri, 17 Oct 2008 09:59:27 -0400 (EDT)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754109AbYJQN7W (ORCPT <rfc822;hmh@hmh.eng.br>);
	Fri, 17 Oct 2008 09:59:22 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753670AbYJQN7W
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 17 Oct 2008 09:59:22 -0400
Received: from mail.suse.de ([195.135.220.2]:40315 "EHLO mx1.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753536AbYJQN7V (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 17 Oct 2008 09:59:21 -0400
Received: from Relay2.suse.de (relay-ext.suse.de [195.135.221.8])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.suse.de (Postfix) with ESMTP id 21312429C6
	for <linux-kernel@vger.kernel.org>; Fri, 17 Oct 2008 16:03:09 +0200 (CEST)
Date: Fri, 17 Oct 2008 15:59:10 +0200
From: Karsten Keil <kkeil@suse.de>
To: linux-kernel@vger.kernel.org
Subject: e1000e EEPROM corruption
Message-ID: <20081017135910.GA18206@pingi.kke.suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Organization: SuSE Linux AG
X-Operating-System: Linux 2.6.16.60-0.27-smp x86_64
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi,

so after this ugly bug is finally fixed, here maybe left some victims of
this bug.

If here is still sombody who need help to recover from this issue,

I can probably help him, I successful recovered all machines on our side,
even one which do not longer show the NIC via lspci, so the only restiction
is, that the machine still boots and we have a NVM image of a similar
machine.
You should know the PCI ids of the NIC from the time before it crashed and
the MAC address.

-- 
Karsten Keil
SuSE Labs
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

--5mCyUwZo2JvN/JJP--