lkml.org 
[lkml]   [2000]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: eepro100 status?
On Mon, Aug 21, 2000 at 01:32:46PM +0100, Tony Hoyle wrote:
> Andrey Savochkin wrote:
> > There are different reasons for "no resource" reports.
> > The first possible is a big traffic bursts exhausting the whole RX ring.
> > This cases are rare.
>
> This is on a home 100MB network with 4 machines on it. Pretty hard to
> saturate
> without going to a lot of effort.
>
> > Some people see "no resource" messages immediately after initialization.
> > It's a bug in the initialization sequence, not completely solved yet.
>
> This must be what I'm seeing. It generally happens after booting.
>
> > But there are known workarounds.
>
> What are they? (editing the network startup to init the device twice?)

Slowdown of the initialization.
I recommend to insert udelay(1) before each wait_for_cmd_done() call from
speedo_resume().

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/

\
 
 \ /
  Last update: 2005-03-22 12:37    [from the cache]
©2003-2011 Jasper Spaans