Re: 2.2.15pre19 (gcc version 2.7.2.3) eth messages

From: Andrew Morton (andrewm@uow.edu.au)
Date: Wed Apr 19 2000 - 21:45:16 EST

"Jeffrey E. Hundstad" wrote:
>
> I've placed 2.2.15pre19 on two of our servers. One is a SMB and ATALK
> file server and the other is a Usenet news server. Both have identical
> hardware. The ethernet card is a eepro100. The SMB/ATALK server is not
> reporting any problems. The news server is spewing the following (below)
> to syslog.
> ...
>
> eth0: Printing Rx ring (next to receive into 936742, dirty index
> 936734).
>

You're getting Tx timeouts.

Andrey, I'm looking at these two statements in speedo_start_xmit():

        clear_suspend(sp->last_cmd);
        /* We want the time window between clearing suspend flag on the
previous
           command and resuming CU to be as small as possible.
           Interrupts in between are very undesired. --SAW */
        outb(CUResume, ioaddr + SCBCmd);

Is there a possibility that the write in clear_suspend() is still stuck
in the CPU's write buffer when the NIC's DMA engine is unstalled?

(Where does one find the eepro datasheet, BTW?) 

-- 
-akpm-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:16 EST