> > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> let me guess: intel eepro100 or similar??
yeap
00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Asustek Computer, Inc.: Unknown device 1043
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 8 min, 56 max, 64 set, cache line size 08
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fd000000 (32-bit, non-prefetchable)
Region 1: I/O ports at d800
Region 2: Memory at fc800000 (32-bit, non-prefetchable)
Capabilities: <available only to root>
> Well known problem with that one. dont know if its fully fixed ... With
> 2.4.0-test9-pre3 it doesnt happen on my machine ...
we have 1-2 servers running 2.4.0-test9 and we got this error ...
is there any patch to 2.2.18pre ? since the server has to run on sunday
we can still make the crazy tests 3 days. it would be cool to fix it to
2.2.X if the bug is known ;)
octave
--
Amicalement,
oCtAvE
"Peu importe ce qu'il y a de l'autre c?t?.
Tout ce qu'on laisse ici n'est qu'une histoire
dont on se souviendra ou pas."
On Thu, 26 Oct 2000, octave klaba wrote:
> > > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> > let me guess: intel eepro100 or similar??
> yeap
er, "me too":
Bus 0, device 2, function 0:
Ethernet controller: Intel 82557 (rev 8).
Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=64. Min Gnt=8.Max Lat=56.
Non-prefetchable 32 bit memory at 0xb5fff000 [0xb5fff000].
I/O at 0x2400 [0x2401].
Non-prefetchable 32 bit memory at 0xb5e00000 [0xb5e00000].
On Debian's 2.2.17-compact on a Compaq DL380 - with 60 days uptime I have
6 "eth0: card reports no resources." messages reported in dmesg.
[...]
> > Well known problem with that one. dont know if its fully fixed ... With
> > 2.4.0-test9-pre3 it doesnt happen on my machine ...
> we have 1-2 servers running 2.4.0-test9 and we got this error ...
>
> is there any patch to 2.2.18pre ? since the server has to run on sunday
> we can still make the crazy tests 3 days. it would be cool to fix it to
> 2.2.X if the bug is known ;)
Unless this is "mostly harmless" a backport of any fix to 2.2.xx would be
received most gratefully.
Thanks,
Neale.
On Fri, 27 Oct 2000, Neale Banks wrote:
> On Thu, 26 Oct 2000, octave klaba wrote:
>
> > > > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> > > let me guess: intel eepro100 or similar??
> > yeap
>
> er, "me too":
>
> Bus 0, device 2, function 0:
> Ethernet controller: Intel 82557 (rev 8).
> Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=64. Min Gnt=8.Max Lat=56.
> Non-prefetchable 32 bit memory at 0xb5fff000 [0xb5fff000].
> I/O at 0x2400 [0x2401].
> Non-prefetchable 32 bit memory at 0xb5e00000 [0xb5e00000].
>
> On Debian's 2.2.17-compact on a Compaq DL380 - with 60 days uptime I have
> 6 "eth0: card reports no resources." messages reported in dmesg.
We are having the same problem with eepro100 on a Compaq DL360.
v1.11 of eepro100.c fixed the problem:
ftp://ftp.scyld.com/pub/network/eepro100.c
On Fri, Oct 27, 2000 at 11:29:08AM -0200, you [Marcelo Tosatti] claimed:
>
>
> On Fri, 27 Oct 2000, Neale Banks wrote:
>
> > On Thu, 26 Oct 2000, octave klaba wrote:
> >
> > > > > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> > > > let me guess: intel eepro100 or similar??
> > > yeap
> >
> > er, "me too":
> >
> > Bus 0, device 2, function 0:
> > Ethernet controller: Intel 82557 (rev 8).
> > Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=64. Min Gnt=8.Max Lat=56.
> > Non-prefetchable 32 bit memory at 0xb5fff000 [0xb5fff000].
> > I/O at 0x2400 [0x2401].
> > Non-prefetchable 32 bit memory at 0xb5e00000 [0xb5e00000].
> >
> > On Debian's 2.2.17-compact on a Compaq DL380 - with 60 days uptime I have
> > 6 "eth0: card reports no resources." messages reported in dmesg.
>
> We are having the same problem with eepro100 on a Compaq DL360.
>
> v1.11 of eepro100.c fixed the problem:
>
> ftp://ftp.scyld.com/pub/network/eepro100.c
The eepro100 problem (2.2.18pre17 stock) happens here too: "card reports
no resources" and then the network stalls for few minutes.
The hack suggested by David Richardson (
http://marc.theaimsgroup.com/?l=linux-kernel&m=96514412914742&w=2)
did not help.
The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
the error messages, but the network still stalls, and worse yet, seems to
stall forever (as opposed to few minutes with 2.2.18pre17 driver).
A network problem is not out of question (although the rest of the network
works just fine, and we did try another HUB port). It could also be flaky
card, but the machine and the card worked fine for years in their past
life under NT.
This is dual PPro200, 256MB, nothing fancy.
-- v --
[email protected]
You should use the Intel e100 driver at
http://support.intel.com/support/network/adapter/pro100/100Linux.htm.
It works much better than eepro100.
Jeff
ASL
----- Original Message -----
From: Ville Herva <[email protected]>
To: <[email protected]>; <[email protected]>
Sent: Friday, October 27, 2000 8:13 AM
Subject: Re: VM-global-2.2.18pre17-7
> On Fri, Oct 27, 2000 at 11:29:08AM -0200, you [Marcelo Tosatti] claimed:
> >
> >
> > On Fri, 27 Oct 2000, Neale Banks wrote:
> >
> > > On Thu, 26 Oct 2000, octave klaba wrote:
> > >
> > > > > > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> > > > > let me guess: intel eepro100 or similar??
> > > > yeap
> > >
> > > er, "me too":
> > >
> > > Bus 0, device 2, function 0:
> > > Ethernet controller: Intel 82557 (rev 8).
> > > Medium devsel. Fast back-to-back capable. IRQ 10. Master
Capable. Latency=64. Min Gnt=8.Max Lat=56.
> > > Non-prefetchable 32 bit memory at 0xb5fff000 [0xb5fff000].
> > > I/O at 0x2400 [0x2401].
> > > Non-prefetchable 32 bit memory at 0xb5e00000 [0xb5e00000].
> > >
> > > On Debian's 2.2.17-compact on a Compaq DL380 - with 60 days uptime I
have
> > > 6 "eth0: card reports no resources." messages reported in dmesg.
> >
> > We are having the same problem with eepro100 on a Compaq DL360.
> >
> > v1.11 of eepro100.c fixed the problem:
> >
> > ftp://ftp.scyld.com/pub/network/eepro100.c
>
> The eepro100 problem (2.2.18pre17 stock) happens here too: "card reports
> no resources" and then the network stalls for few minutes.
>
> The hack suggested by David Richardson (
> http://marc.theaimsgroup.com/?l=linux-kernel&m=96514412914742&w=2)
> did not help.
>
> The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
> the error messages, but the network still stalls, and worse yet, seems to
> stall forever (as opposed to few minutes with 2.2.18pre17 driver).
>
> A network problem is not out of question (although the rest of the network
> works just fine, and we did try another HUB port). It could also be flaky
> card, but the machine and the card worked fine for years in their past
> life under NT.
>
> This is dual PPro200, 256MB, nothing fancy.
>
>
> -- v --
>
> [email protected]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> Please read the FAQ at http://www.tux.org/lkml/
> You should use the Intel e100 driver at
> http://support.intel.com/support/network/adapter/pro100/100Linux.htm.
> It works much better than eepro100.
Thats not the general consensus, but its worth trying in case it works best
for a given problem. In paticular it knows about bugs with combinations of
transceivers which the eepro100 driver does not.
Alan,
I agree with your point. In term of usability, the e100 driver has a wider
range of support for the Intel NIC cards.
Jeff
----- Original Message -----
From: Alan Cox <[email protected]>
To: Jeff Nguyen <[email protected]>
Cc: Ville Herva <[email protected]>;
<[email protected]>; <[email protected]>
Sent: Friday, October 27, 2000 10:16 AM
Subject: Re: VM-global-2.2.18pre17-7
> > You should use the Intel e100 driver at
> > http://support.intel.com/support/network/adapter/pro100/100Linux.htm.
> > It works much better than eepro100.
>
> Thats not the general consensus, but its worth trying in case it works
best
> for a given problem. In paticular it knows about bugs with combinations of
> transceivers which the eepro100 driver does not.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> Please read the FAQ at http://www.tux.org/lkml/
> The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
> the error messages,
yes. even is setup is not clean, it seems to work with 24-25Mbs since
I have no errors.
> but the network still stalls, and worse yet, seems to
> stall forever (as opposed to few minutes with 2.2.18pre17 driver).
after 2h it still works. maybe it will crash later. check it later.
octave
>The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
>the error messages, but the network still stalls, and worse yet, seems to
>stall forever (as opposed to few minutes with 2.2.18pre17 driver).
this eepro100.c works for me
asus/dual piii-800 133mhz/768ram ecc/mylex-170/2x18Go
thanks for your help.
Octave