[eepro100] Re: system hangs @ boot-time when bringing up eth0

Krawl, Roeland RKrawl@microtest.com
Thu, 7 Sep 2000 17:07:38 -0700 

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01928.CC44F6E0
Content-Type: text/plain

I believe that the "No buffers" and "No resources" problem would get fixed a
lot sooner if Intel would permit the free flow of information about
controlling the 82557, 82558, and 82559. Perhaps the day will come when a
programmer's model of the chip can be obtained without having to sign an NDA
to obtain the super secret programmer's model. It would seem logical that
Ethernet chip manufacturers would want to assist driver developers in any
way they could to improve the robustness of drivers and to boost
sales/popularity of their chips.

Can anyone say concretely that the "No buffers" and "No resources" problem
occurs only with the 82559 chip?

> -----Original Message-----
> From:	Derek Glidden [SMTP:dglidden@illusionary.com]
> Sent:	Thursday, September 07, 2000 7:55 AM
> To:	decouto@lcs.mit.edu; eepro100@scyld.com
> Subject:	Re: [eepro100] Re: system hangs @ boot-time when bringing up
> eth0
> 
> Douglas De Couto wrote:
> > 
> > hi
> > 
> > it is a kernel crash (keyboard lights don't work!) and i have to power
> > cycle.
> > 
> > i lied -- it doesn't always crash when i insmod, sometimes when i ifup
> > the interface.
> 
> Your problem sounds an awful lot like the problem I've been seeing
> lately (and a lot of other people too) with later versions of the
> eepro100 driver.  Check if your syslog reports "Card reports no buffers"
> or "Card reports no resources" from the eepro100 driver.  If so, you've
> run into this initialization bug.  From what I've gathered on this
> issue, there's no quick solution.  It seems that by turning the card
> from MMIO to PIO mode is a "solution" but AFAIC, this is a very klugy
> way of fixing a driver bug.
> 
> -- 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> With Microsoft products, failure is not           Derek Glidden
> an option - it's a standard component.      http://3dlinux.org/
> Choose your life.  Choose your            http://www.tbcpc.org/
> future.  Choose Linux.              http://www.illusionary.com/
> 
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100

------_=_NextPart_001_01C01928.CC44F6E0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">



RE: [eepro100] Re: system hangs @ boot-time when bringing up =
eth0




I believe that the =
"No buffers" and "No resources" problem would get =
fixed a lot sooner if Intel would permit the free flow of information =
about controlling the 82557, 82558, and 82559. Perhaps the day will =
come when a programmer's model of the chip can be obtained without =
having to sign an NDA to obtain the super secret programmer's model. It =
would seem logical that Ethernet chip manufacturers would want to =
assist driver developers in any way they could to improve the =
robustness of drivers and to boost sales/popularity of their =
chips.



Can anyone say =
concretely that the "No buffers" and "No resources" =
problem occurs only with the 82559 chip?




------_=_NextPart_001_01C01928.CC44F6E0--