mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	auke-jan.h.kok@intel.com, bunk@stusta.de, jgarzik@pobox.com,
	saw@saw.sw.com.sg
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Mon, 27 Nov 2006 12:34:06 -0800	[thread overview]
Message-ID: <4807377b0611271234l131bf7d7l975ed7e46d8c7444@mail.gmail.com> (raw)
In-Reply-To: <456AF37C.8090304@privacy.net>

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

On 11/27/06, John <me@privacy.net> wrote:
> John wrote:
>
> >> 00000000-0009ffff : System RAM
> >> 000a0000-000bffff : Video RAM area
> >> 000f0000-000fffff : System ROM
> >> 00100000-0ffeffff : System RAM
> >>   00100000-00296a1a : Kernel code
> >>   00296a1b-0031bbe7 : Kernel data
> >> 0fff0000-0fff2fff : ACPI Non-volatile Storage
> >> 0fff3000-0fffffff : ACPI Tables
> >> 20000000-200fffff : 0000:00:08.0
> >> 20100000-201fffff : 0000:00:09.0
> >> 20200000-202fffff : 0000:00:0a.0
> >> e0000000-e3ffffff : 0000:00:00.0
> >> e5000000-e50fffff : 0000:00:08.0
> >> e5100000-e51fffff : 0000:00:09.0
> >> e5200000-e52fffff : 0000:00:0a.0
> >> e5300000-e5300fff : 0000:00:08.0
> >> e5301000-e5301fff : 0000:00:0a.0
> >> e5302000-e5302fff : 0000:00:09.0
> >> ffff0000-ffffffff : reserved
> >>
> >> I've also attached:
> >>
> >> o config-2.6.18.1-adlink used to compile this kernel
> >> o dmesg output after the machine boots
> >
> > I suppose the information I've sent is not enough to locate the
> > root of the problem. Is there more I can provide?
>
> Here is some context for those who have been added to the CC list:
> http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
>
> As far as I understand, some consider the eepro100 driver to be
> obsolete, and it has been considered for removal.
>
> What is the current status?
>
> Unfortunately, e100 does not work out-of-the-box on this system.
>
> Is there something I can do to improve the situation?

lets go ahead and print the output from e100_load_eeprom
debug patch attached.

[-- Attachment #2: e100_debug.patch --]
[-- Type: application/octet-stream, Size: 849 bytes --]

[e100] debug eeprom problems

Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>

---

 drivers/net/e100.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/net/e100.c b/drivers/net/e100.c
index 19ab344..376ff2d 100644
--- a/drivers/net/e100.c
+++ b/drivers/net/e100.c
@@ -746,10 +746,12 @@ static int e100_eeprom_load(struct nic *
 
 	/* Try reading with an 8-bit addr len to discover actual addr len */
 	e100_eeprom_read(nic, &addr_len, 0);
+	DPRINTK(PROBE, INFO, "addr_len 0x%04X\n", addr_len);
 	nic->eeprom_wc = 1 << addr_len;
 
 	for(addr = 0; addr < nic->eeprom_wc; addr++) {
 		nic->eeprom[addr] = e100_eeprom_read(nic, &addr_len, addr);
+		DPRINTK(PROBE, INFO, "eeprom[%d] = 0x%04X\n", addr, nic->eeprom[addr]);
 		if(addr < nic->eeprom_wc - 1)
 			checksum += cpu_to_le16(nic->eeprom[addr]);
 	}

  reply	other threads:[~2006-11-27 20:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 17:28 John
2006-11-04  1:46 ` H. Peter Anvin
2006-11-04  6:22   ` thockin
2006-11-04  6:28     ` thockin
2006-11-07 11:23   ` John
2006-11-07 17:17     ` H. Peter Anvin
2006-11-07 17:43       ` Auke Kok
2006-11-07 18:27         ` H. Peter Anvin
2006-11-07 18:34           ` Auke Kok
2006-11-07 18:38             ` H. Peter Anvin
2006-11-08 10:55     ` John
2006-11-08 16:17       ` Auke Kok
2006-11-09 12:17         ` John
2006-11-09 17:03           ` Auke Kok
2006-11-08 17:26       ` Jesse Brandeburg
2006-11-09 14:15         ` John
2006-11-10  0:19           ` Jesse Brandeburg
2006-11-10 12:03             ` John
2006-11-15  8:34               ` John
2006-11-27 14:17                 ` John
2006-11-27 20:34                   ` Jesse Brandeburg [this message]
2006-11-29 11:26                     ` John
2006-11-29 18:55                       ` Jesse Brandeburg
     [not found]                         ` <45704001.9040108@privacy.net>
2006-12-04 23:26                           ` Jesse Brandeburg
     [not found] <fa.FcMVUlqOXU3cAnxsPEN6d8T0wxU@ifi.uio.no>
     [not found] ` <fa.0FC8eT8GQaLxmNQTrsqyNFjRK4E@ifi.uio.no>
     [not found]   ` <fa.nds0CFkNbotWh4VNM05EixY68wE@ifi.uio.no>
     [not found]     ` <fa.K3Gpuu7oYQv+4q85Ziy3ljV6u+E@ifi.uio.no>
     [not found]       ` <fa./RNOPU0DwWMrnKJSqlMaY+Y16JM@ifi.uio.no>
     [not found]         ` <fa.yV32AYzot0OkvPVCY7VTCvd6rJw@ifi.uio.no>
2007-02-07 11:06           ` John
2007-02-13 19:45             ` Brandeburg, Jesse
2007-08-14 16:35 Amin Azez

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=4807377b0611271234l131bf7d7l975ed7e46d8c7444@mail.gmail.com \
    --to=jesse.brandeburg@gmail.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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

all inboxes | Powered by JetHome®