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: Wed, 29 Nov 2006 10:55:54 -0800	[thread overview]
Message-ID: <4807377b0611291055o6e28c66ft9edeb3c8363dd49b@mail.gmail.com> (raw)
In-Reply-To: <456D6E5C.4040805@privacy.net>

On 11/29/06, John <me@privacy.net> wrote:
> > Let's go ahead and print the output from e100_load_eeprom
> > debug patch attached.
>
> Loading (then unloading) e100.ko fails the first few times (i.e. the
> driver claims one of the EEPROMs is corrupted). Thereafter, sometimes it
> fails, other times it works. Sounds like a race, no?

yes, or something like that.  I think you may have a piece of eeprom
hardware that is either "slow" or slightly out of spec.  I wonder if
the hrt kernel makes udelay(4) much more like 4us than the regular
kernels.

can you try adding mdelay(100); in e100_eeprom_load before the for loop,
and then change the multiple udelay(4) to mdelay(1) in e100_eeprom_read

> On an unrelated note, insmod_100.txt is truncated at the beginning, and
> insmod_110.txt is truncated in the middle (!!) cf. line 14. What would
> cause klogd to behave like that?

usually its because whatever is printing is printing too fast or too
much at a time.

  reply	other threads:[~2006-11-29 18:55 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
2006-11-29 11:26                     ` John
2006-11-29 18:55                       ` Jesse Brandeburg [this message]
     [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=4807377b0611291055o6e28c66ft9edeb3c8363dd49b@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®