I've been seeing the same kind of messages with an eepro100
but they don't happen when the module is loaded. They
happen after it has been running for a few days. I am
running 2.4.1. I haven't seen any real problems but these
messages still scare me.
Micah
>
> On Fri, 2 Feb 2001, Ivan Passos wrote:
> >
> > On Fri, 2 Feb 2001, Ion Badulescu wrote:
> >
> > > On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos
<[email protected]> wrote:
> > >
> > > > Sometimes when I reboot the system, as soon as the
eepro100 module is
> > > > loaded, I start to get these msgs on the screen:
> > > >
> > > > eth0: card reports no resources.
> > > > eth0: card reports no RX buffers.
> > > > eth0: card reports no resources.
> > > > eth0: card reports no RX buffers.
> > > > eth0: card reports no resources.
> > > > eth0: card reports no RX buffers.
> > > > (...)
> > >
> > > Does the following patch, taken from 2.4.1, help?
> >
> > I'm currently testing. I'll get back to you soon (have
to reboot the
> > system a lot to make sure it's really solved ... :)).
>
> Yes, the patch did solve the problem.
>
> Alan, could you please include this patch on your
2.2.19pre series (if
> it's not already included)??
>
> Ion, thanks again for your help!!
>
> Later,
> Ivan
>
> --- linux-2.2.18/drivers/net/eepro100-old.c Fri Feb
2 15:30:23 2001
> +++ linux-2.2.18/drivers/net/eepro100.c Fri Feb 2
15:33:19 2001
> @@ -751,6 +751,7 @@
> This takes less than 10usec and will easily
finish before the next
> action. */
> outl(PortReset, ioaddr + SCBPort);
> + inl(ioaddr + SCBPort);
> /* Honor PortReset timing. */
> udelay(10);
>
> @@ -839,6 +840,7 @@
> #endif /* kernel_bloat */
>
> outl(PortReset, ioaddr + SCBPort);
> + inl(ioaddr + SCBPort);
> /* Honor PortReset timing. */
> udelay(10);
>
> @@ -1062,6 +1064,9 @@
> /* Set the segment registers to '0'. */
> wait_for_cmd_done(ioaddr + SCBCmd);
> outl(0, ioaddr + SCBPointer);
> + /* impose a delay to avoid a bug */
> + inl(ioaddr + SCBPointer);
> + udelay(10);
> outb(RxAddrLoad, ioaddr + SCBCmd);
> wait_for_cmd_done(ioaddr + SCBCmd);
> outb(CUCmdBase, ioaddr + SCBCmd);
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-
info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Sun, Feb 25, 2001 at 07:14:09AM +0000, angelcode wrote:
> I've been seeing the same kind of messages with an eepro100
> but they don't happen when the module is loaded. They
> happen after it has been running for a few days. I am
> running 2.4.1. I haven't seen any real problems but these
> messages still scare me.
If your network isn't stuck, it's not a real problem.
The card just reports that it feels shortage of receive buffers.
It may be real or illusional one, it's not a really big problem.
Best regards
Andrey
> > > > On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos
> <[email protected]> wrote:
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > (...)