On Mon, 22 May 2000, Petko Manolov wrote:
> Johannes Erdfelt wrote:
> >
> > Yeah, I suspected the same error from my driver.
> >
> > It still kinda looks like a pegasus driver problem. I'm curious why it
> > thought the Tx timed out.
>
>
> Every time when start_xmit is called the watchdog timer is reseted.
> So if within this interval (in pegasus' case 5sec) there is no another
> call of start_xmit, the driver is warned by calling
> pegasus_tx_timeout.
>
>
> > I bet you it needs something like this line in pegasus_start_xmit:
> >
> > warn("%s: Tx timed out. Reseting...", net->name);
> > + usb_unlink_urb(&pegasus->tx_urb);
> >
> > Of course, I know nothing about network drivers under Linux so this is
> > just an educated guess.
>
>
> This looks reasonable. I'll try and will post comments ;-)
I added this code to start_xmit and tried it out with both the usb-uchi
and uhci drivers and my transfer of 750Megs finished. It still
timed out a couple of times during transfer, but it completed with an
average speed of 370KBytes/sec for usb-uchi and 320KBytes/sec for uhci.
For reason the uhci driver caused more timeout messages.
On a related note, on a ohci based system with the same nic, I am getting
pegasus.c; RX timeout -110 messages. Not sure what the problem is there
either.
Thanks,
-Jason Sharpee
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
