netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Mark Lord <mlord@pobox.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	David Laight <David.Laight@ACULAB.COM>
Subject: Re: Help testing for USB ethernet/xHCI regression
Date: Wed, 29 Jan 2014 13:18:17 -0800	[thread overview]
Message-ID: <20140129211817.GA5991@xanatos> (raw)
In-Reply-To: <52E883FB.7010704@pobox.com>

On Tue, Jan 28, 2014 at 11:30:51PM -0500, Mark Lord wrote:
> On 14-01-28 03:30 PM, Sarah Sharp wrote:
> ..
> > Can you please pull this branch, which contains a 3.13 kernel with
> > David's patch reverted, and test whether your USB ethernet device works
> > or fails?
> 
> Fails.  dmesg log attached.

It's funny, because there's certainly data transferred over endpoint
0x82, even though there were link TRBs in the middle of transfers.  Did
the "untransferred" messages stop when the device stopped working, or
did they continue?

> All I do is something akin to this:
> 
>    mount /server/ /x
>    mount --bind / /t
>    mirrordir -v --strict-mtimes /t /x/backups/empress
> 
> "mirrordir" is similar to "rsync", but less cryptic.
> The sequence above maintains a clone of the root filesystem
> of my ultrabook ("empress") on an NFS server over GigE.

Please send me the output of `sudo lsusb -t`  and `sudo lsusb -v` with
the USB device attached.  I'd like to know whether you and David have
the same device and driver.  Perhaps the link TRB issue only impacts
that device, and we can limit scatter-gather under xHCI for that device.
If not, we'll have to look at bigger fixes.

Sarah Sharp

  parent reply	other threads:[~2014-01-29 21:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 20:30 Help testing for USB ethernet/xHCI regression Sarah Sharp
2014-01-29  4:30 ` Mark Lord
2014-01-29  4:54   ` Mark Lord
2014-01-29 21:18   ` Sarah Sharp [this message]
2014-01-30 10:03     ` David Laight
2014-01-30 21:45     ` Mark Lord
     [not found] <22081260.RNay0J72dY@athas>
2014-01-29 21:54 ` Sarah Sharp
2014-01-30  9:44   ` David Laight
2014-01-30 10:46     ` renevant
2014-01-30 12:46       ` renevant
     [not found]     ` <063D6719AE5E284EB5DD2968C1650D6D0F6ACF20-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-01-30 18:44       ` Sarah Sharp
2014-01-30 19:45         ` Mark Lord
2014-01-30 19:54         ` Paul Zimmerman
     [not found]           ` <A2CA0424C0A6F04399FB9E1CD98E03046D147453-Yu2iAY70zvrYN67daEjeMPufCSb+aD3WLzEdoUbNIic@public.gmane.org>
2014-01-30 20:00             ` Mark Lord
2014-01-30 21:41               ` Sarah Sharp
2014-01-30 22:20                 ` Mark Lord
     [not found]                   ` <52EAD038.5020409-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2014-01-30 23:26                     ` Sarah Sharp
2014-01-31  2:32                       ` Mark Lord
2014-01-31 18:37                         ` Sarah Sharp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140129211817.GA5991@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).