2.2.18: weird eepro100 msgs
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
Quoted 6 lines · Ivan Passos
Quoted 4 lines · Ion Badulescu
Quoted 2 lines
On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos
Quoted 2 lines · <[email protected]> wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Sometimes when I reboot the system, as soon as the
eepro100 module is
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
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. (...)
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
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
Quoted 5 lines
Quoted 1 line
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
Quoted 8 lines
it's not already included)??
Ion, thanks again for your help!!
Later,
Ivan---
linux-2.2.18/drivers/net/eepro100-old.cFri Feb
2 15:30:23 2001
Quoted 1 line
+++
linux-2.2.18/drivers/net/eepro100.cFri Feb 2
15:33:19 2001
Review line 751
Quoted 2 lines
(quoted diff) +0
-0@@ -751,6 +751,7 @@ This takes less than 10usec and will easily
finish before the next
Quoted 26 lines
(quoted diff) +5
-1action. */ 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); -
Quoted 1 line
To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
Quoted 2 lines
the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-
info.html
Quoted 2 lines
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines · angelcode
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
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos
Quoted 7 lines · <[email protected]> wrote:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
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. (...)