Messages in this thread |  | | Date | Tue, 18 Mar 2003 19:18:33 -0800 | From | Andrew Morton <> | Subject | Re: 2.5.65-mm1: eth0: Transmit error, Tx status register 90 |
| |
"Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> wrote: > > Hi, > > I've been benchmarking file copy operations between 2.5.65-mm1 > and 2.4.20-2.51 since I have noticed that transferring files from my > 2.4.20 machine to 2.5.65-mm1 gives an steady 10MBps throughput > but doing the opposite (from 2.5.65-mm1 to 2.4.20) gives me a > mere 3MBps throughput.
Is it slow with both scp and NFS? Or just NFS?
If just NFS then yes, I see this too. Transferring files 2.5->2.4 over NFS is several times slower than 2.4->2.4 or 2.5->2.5. Quite repeatable.
> After transferring a 256MB file using NFS and SCP, I have noticed > several "eth0: Transmit error, Tx status register 90.". I have attached > dmesg output, ioports, iomem, lsmod and lspci.
That's a transmit underrun. The PCI/memory system was not able to feed data into the NIC fast enough.
Please determine when this started. 2.5.64 would be a good kernel to test because it doesn't have the PCI changes.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |