[eepro100] eth0: card reports no resources.

Dimitris Zilaskos dzila@tassadar.physics.auth.gr
Fri Apr 26 01:59:01 2002


  Hello ,

 I am using linux 2.4.18-ac3 on a dual Pentium 2 266 system
(Linux ftp 2.4.18-ac3 #1 SMP Thu Mar 28 22:48:49 EET 2002 i686
unknown). lspci shows

0:00.0 Host bridge: Intel Corporation 440LX/EX - 82443LX/EX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corporation 440LX/EX - 82443LX/EX AGP bridge
(rev 03)
00:04.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01)
00:04.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:04.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01)
00:06.0 SCSI storage controller: Adaptec AIC-7880U
00:0a.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 08)
01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 01)

 Yesterday it has been a rather busy day for the box ( it servers as an
ftp server ) and I noticed those messages in the logfiles

Apr 25 19:55:04 ftp kernel: eth0: card reports no resources.
Apr 25 19:55:04 ftp kernel: eth0: card reports no resources.
Apr 25 20:03:08 ftp kernel: eth0: card reports no resources.
Apr 25 20:03:08 ftp kernel: eth0: Too much work at interrupt,
status=0x4090.

  I searched around a bit and it appears that in the past that message was
followed by loss of network connectivity . In my case there has been
nothing noticable , apart from those entries in the logs .
 At the time those entries occured the card was working at around 900
kbytes/sec in both directions . I have not observed any messages when
doing transfers in our lan with speeds like 9-10 Mbytes/sec . The time the
message occured the ftp server was crowded with many clients dowloading
various  files from the internet , which we connect to at 10 Mbps .
  It seems strange to me for that message to be generated when the card is
working at roughly 1/10 of its supposed full capacity , so I though to
ask what do you think of it . I understand that in this case it is not the
size of the transfers but the flow of packets that causes it , but it still
doesnt seem ok to me that this should be generated from a 10 Mbps uplink ,
though I have not noticed any network connectivity issues despite those
messages .

 Kind regards ,

--
=============================================================================

Dimitris Zilaskos

Department of Physics @ Aristotle Univercity of Thessaloniki , Greece
=============================================================================