I just tried 3.14 as well with the same results. RX status -110 followed
by TX status -110 messages and eth0 dropout.
I noticed that the interrupt is being pulled and apparently there is
nothing in the buffer (actual data size) for the data, compared to what
it was expecting yielding the -110 message which gets passed back to the
driver. Is this indicative that the physical device (Linksys 10/100) is
getting confused and not responding to the HC driver request for data
and/or is this a congestion issue of traffic on the USB bus and missing a
control message? Does a -110 urb status happen quite often, or is this
just a problem I am experiencing with my system configuration?
The driver / device seem to deadlock on this failed data item and eth0
stops xmitting data, hence my problem.
Thanks for your time!
-Jason
On Fri, 9 Jun 2000, Rick Richardson wrote:
> On Fri, Jun 09, 2000 at 01:58:56PM -0700, Stephen J. Gowdy wrote:
> > Hi Rick,
> > There is now a 3.14 version of the pegasus driver. Not sure it
> > will make any difference though, but you might want to try it, I've
> > attached it.
>
> Thanks for the newer driver. But I'm still seeing the same NFS
> problems -- MP3 dropouts when rsize,wsize=1024, and also NFS server
> not responding...OK when the size is bigger than that.
>
> My guess is its a receive side problem (dropped packets?). I suppose
> I should collect some tcpdumps on the NFS server and on the client
> (the iOpener), then start digging into the code.
>
> -Rick
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
