All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Madden <jmadden@ivy.tec.in.us>
To: Masaru Kawashima <masaru@scji.toshiba-eng.co.jp>,
	Dionysius Wilson Almeida <dwilson@technolunatic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100: wait_for_cmd_done timeout
Date: Thu, 21 Jun 2001 09:37:47 -0500	[thread overview]
Message-ID: <0106210940470C.28098@ycn013> (raw)
In-Reply-To: <20010620163134.A22173@technolunatic.com> <20010621231939.757bddd6.masaru@scji.toshiba-eng.co.jp>
In-Reply-To: <20010621231939.757bddd6.masaru@scji.toshiba-eng.co.jp>

> Dionysius Wilson Almeida <Dionysius Wilson Almeida <dwilson@technolunatic.com>> wrote:
> > Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> > Jun 20 16:14:38 debianlap last message repeated 5 times
> 
> I saw the same message.
> 
> The comment before wait_for_cmd_done() function in
> linux/drivers/net/eepro100.c says:
> /* How to wait for the command unit to accept a command.
>    Typically this takes 0 ticks. */
> 
> And the initial value for the bogus counter, named "wait", is 1000.
> Is it enough for your machine?
> 
> I applied attached patch, eepro100.patch.  After that, I've never seen
> the message from wait_for_cmd_done().  And, my NIC works fine.
> 
> You may want to adjust the initial value for the bogus counter.
> I don't know the appropriate value for this bogus counter.

int wait is set to 20000 in my eepro100.c (stock 2.2.19), and I still get these
errors.  Think the patch with the udelay() will still work?

John




-- 
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivy.tec.in.us

  reply	other threads:[~2001-06-21 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 23:31 eepro100: wait_for_cmd_done timeout Dionysius Wilson Almeida
2001-06-20 23:51 ` Andrey Savochkin
2001-06-21  0:02   ` Dionysius Wilson Almeida
2001-06-21 13:46     ` Rafael Martinez
2001-06-22  1:36     ` Dionysius Wilson Almeida
2001-06-22 13:31       ` Andrey Savochkin
2001-06-22 20:06         ` Dionysius Wilson Almeida
2001-06-21 14:19 ` Masaru Kawashima
2001-06-21 14:37   ` John Madden [this message]
2001-06-22  1:27     ` Masaru Kawashima
2001-06-21 16:28   ` Masaru Kawashima
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 16:56 Paul Rolland
2003-02-27 20:30 ` Andrey Nekrasov
2003-02-28  6:50   ` Paul Rolland
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik

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=0106210940470C.28098@ycn013 \
    --to=jmadden@ivy.tec.in.us \
    --cc=dwilson@technolunatic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masaru@scji.toshiba-eng.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.