From: Ivan Passos <lists@cyclades.com>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.2.18: weird eepro100 msgs
Date: Fri, 23 Feb 2001 17:53:39 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10102231738400.32459-100000@main.cyclades.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10102021719120.3255-100000@main.cyclades.com>
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 <lists@cyclades.com> 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);
next prev parent reply other threads:[~2001-02-24 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 23:01 2.2.18: weird eepro100 msgs Ivan Passos
2001-02-02 23:35 ` Ion Badulescu
2001-02-03 1:20 ` Ivan Passos
2001-02-24 1:53 ` Ivan Passos [this message]
2001-02-25 7:14 angelcode
2001-02-27 2:09 ` Andrey Savochkin
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=Pine.LNX.4.10.10102231738400.32459-100000@main.cyclades.com \
--to=lists@cyclades.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).