[eepro100] "Transmit timed out:" when activating the interface
erik gostischa franta
frost@proximitygroup.com
Fri, 29 Dec 2000 07:54:23 -0500
--------------070806090205000002010904
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Donald Becker wrote:
> On Wed, 27 Dec 2000, erik gostischa franta wrote:
>
>> I just just compiled a 2.2.18 kernel from the vanilla source .
>> on a dual pentium box with two Intel EEPRO interfaces.
>> rev 5 & rev 9 I think
>> and I am using the newest 1.12 eepro driver from donald becker.
>>
>> well, everything seems to work fine..except:
>> at boot up (or everytime I restart the network of course)
>> I get folowing error message:
>>
>> eth0: Transmit timed out: status 0000 0090 at 0/7 commands 0001a000
>> 00020000 00030000
>
> ...
>
>> a dmesg dump gives me:
>>
>> eth0: Tx ring dump, Tx queue 7 / 0:
>> eth0: * 0 0001a000.
>> eth0: 1 00020000.
>> eth0: 2 00030000.
>> eth0: 3 00030000.
>> eth0: 4 00030000.
>> eth0: 5 00030000.
>> eth0: 6 40030000.
>> eth0: =7 00000000.
>
>
> There are three commands types on the command list.
> 0001 Station Address setup
> 0002 Configure command
> 0003 Multicast setup (several)
>
> Only the first command has completed, and not the subsequent commands.
> The multicast setup commands are queued every two seconds whenever the no
> packets have been received to work around an obscure Rx bug.
>
> The status is
> Tx command unit active
> Rx unit ready.
>
> Usually I would suggest that the card is having bus-master problems, but the
> first command completed and wrote back an 'OK' status. The chip is hanging
> on the configure command. This command is complex, but it shouldn't cause
> any bus traffic.
>
>> eth0:Printing Rx ring (next to receive into 0).
>> Rx ring entry 0 00000001.
>
>
> Sure 'nuf, no packets have been received.
>
>> eth0: Tx ring dump, Tx queue 7 / 0:
>> eth0: * 0 0001a000.
>> eth0: 1 00020000.
>
>
> Some story after the reset. The configure command is taking forever to
> complete.
>
> Does the interface eventually start after this problem? Or is it
> permanently hosed?
>
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
> Annapolis MD 21403 410-990-9993
>
>
well, I guess the interface starts up, this is what I did.
I did a 2.5GB transfer using tar and piping it into ssh and everything
works fine.
and the thing has been up for several days now, everything seem to work
fine.
I know, you might say: "it works, dont complain" :)
but as I said I am really concerned about the stability of this box,
since it will be our
main server.
thx alot, erik
--------------070806090205000002010904
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html><head></head><body>Donald Becker wrote:<br>
<blockquote type="cite" cite="mid:Pine.LNX.4.10.10012291153590.18565-100000@vaio.greennet"><pre wrap="">On Wed, 27 Dec 2000, erik gostischa franta wrote:<br><br></pre>
<blockquote type="cite"><pre wrap="">I just just compiled a 2.2.18 kernel from the vanilla source .<br>on a dual pentium box with two Intel EEPRO interfaces.<br>rev 5 & rev 9 I think<br>and I am using the newest 1.12 eepro driver from donald becker.<br><br>well, everything seems to work fine..except:<br>at boot up (or everytime I restart the network of course)<br>I get folowing error message:<br><br>eth0: Transmit timed out: status 0000 0090 at 0/7 commands 0001a000 <br>00020000 00030000<br></pre></blockquote>
<pre wrap=""><!---->...<br></pre>
<blockquote type="cite"><pre wrap="">a dmesg dump gives me:<br><br>eth0: Tx ring dump, Tx queue 7 / 0:<br>eth0: * 0 0001a000.<br>eth0: 1 00020000.<br>eth0: 2 00030000.<br>eth0: 3 00030000.<br>eth0: 4 00030000.<br>eth0: 5 00030000.<br>eth0: 6 40030000.<br>eth0: =7 00000000.<br></pre></blockquote>
<pre wrap=""><!----><br>There are three commands types on the command list.<br>0001 Station Address setup<br>0002 Configure command<br>0003 Multicast setup (several)<br><br>Only the first command has completed, and not the subsequent commands.<br>The multicast setup commands are queued every two seconds whenever the no<br>packets have been received to work around an obscure Rx bug.<br><br>The status is<br> Tx command unit active<br> Rx unit ready.<br><br>Usually I would suggest that the card is having bus-master problems, but the<br>first command completed and wrote back an 'OK' status. The chip is hanging<br>on the configure command. This command is complex, but it shouldn't cause<br>any bus traffic.<br><br></pre>
<blockquote type="cite"><pre wrap="">eth0:Printing Rx ring (next to receive into 0).<br>Rx ring entry 0 00000001.<br></pre></blockquote>
<pre wrap=""><!----><br>Sure 'nuf, no packets have been received.<br><br></pre>
<blockquote type="cite"><pre wrap="">eth0: Tx ring dump, Tx queue 7 / 0:<br>eth0: * 0 0001a000.<br>eth0: 1 00020000.<br></pre></blockquote>
<pre wrap=""><!----><br>Some story after the reset. The configure command is taking forever to<br>complete.<br><br>Does the interface eventually start after this problem? Or is it<br>permanently hosed?<br><br>Donald Becker <a class="moz-txt-link-abbreviated" href="mailto:becker@scyld.com">becker@scyld.com</a><br>Scyld Computing Corporation <a class="moz-txt-link-freetext" href="http://www.scyld.com">http://www.scyld.com</a><br>410 Severn Ave. Suite 210 Second Generation Beowulf Clusters<br>Annapolis MD 21403 410-990-9993<br><br><br></pre>
</blockquote>
well, I guess the interface starts up, this is what I did.<br>
I did a 2.5GB transfer using tar and piping it into ssh and everything works fine.<br>
and the thing has been up for several days now, everything seem to work fine.<br>
<br>
I know, you might say: "it works, dont complain" :)<br>
<br>
but as I said I am really concerned about the stability of this box, since it will be our<br>
main server.<br>
<br>
thx alot, erik<br>
</body></html>
--------------070806090205000002010904--