Messages in this thread |  | | Date | Mon, 21 Aug 2000 13:32:46 +0100 | From | Tony Hoyle <> | Subject | Re: eepro100 status? |
| |
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?)
Tony - 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/
|  |