All of lore.kernel.org
 help / color / mirror / Atom feed
From: angelcode <angelcode@myrealbox.com>
To: lists@cyclades.com, ionut@moisil.cs.columbia.edu,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re:  Re: 2.2.18: weird eepro100 msgs
Date: Sun, 25 Feb 2001 07:14:09 GMT	[thread overview]
Message-ID: <983085249.280angelcode@myrealbox.com> (raw)

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 
<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);
> 
> -
> To unsubscribe from this list: send the line "unsubscribe 
linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-
info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



             reply	other threads:[~2001-02-25  7:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-25  7:14 angelcode [this message]
2001-02-27  2:09 ` 2.2.18: weird eepro100 msgs 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=983085249.280angelcode@myrealbox.com \
    --to=angelcode@myrealbox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ionut@moisil.cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@cyclades.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.