mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: huggie@earth.li
Cc: eepro100@scyld.com, linux-kernel@vger.kernel.org
Subject: Re: eepro cmd_wait
Date: Thu, 18 Jan 2001 20:17:31 +0800	[thread overview]
Message-ID: <20010118201731.A8492@saw.sw.com.sg> (raw)
In-Reply-To: <20010118131011.B19784@the.earth.li>
In-Reply-To: <20010118131011.B19784@the.earth.li>; from "Simon Huggins" on Thu, Jan 18, 2001 at 01:10:11PM

Hi,

On Thu, Jan 18, 2001 at 01:10:11PM +0100, Simon Huggins wrote:
> We have a server running 2.2.18 + RAID which has an eepro100 in it.
> It's connected to a Dlink DFE 816 100 16port 100baseTX hub.
> 
> When the machine boots we get a whole series of timeout errors.
> 
> Jan 18 11:58:09 miguet kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)!
> Jan 18 11:58:09 miguet kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)!
> Jan 18 11:58:09 miguet kernel: eepro100: cmd_wait for(0xffffff90) timedout with(0xffffff90)!
> Jan 18 11:58:38 miguet last message repeated 38 times
> Jan 18 11:58:50 miguet last message repeated 12 times

Could you try to add
	inl(ioaddr + SCBPointer);
	udelay(10);
before
	outb(RxAddrLoad, ioaddr + SCBCmd);
in speedo_resume()?

These two line are a workaround for the RxAddrLoad timing bug, developed by
Donald Becker.  wait_for_cmd_done timeouts may be related to this bug, too.

Best regards
					Andrey V.
					Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2001-01-18 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010118131011.B19784@the.earth.li>
2001-01-18 12:17 ` Andrey Savochkin [this message]
2001-01-18 12:42   ` Simon Huggins
2001-01-18 13:03     ` Andrey Savochkin

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=20010118201731.A8492@saw.sw.com.sg \
    --to=saw@saw.sw.com.sg \
    --cc=eepro100@scyld.com \
    --cc=huggie@earth.li \
    --cc=linux-kernel@vger.kernel.org \
    /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®