All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Hylke Hellinga <hylke.hellinga@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller causing random full speed USB resets
Date: Wed, 14 Jul 2021 10:54:23 -0400	[thread overview]
Message-ID: <20210714145423.GB380727@rowland.harvard.edu> (raw)
In-Reply-To: <CABUoX8tX6+JpPRz7oyJV2fsiEbWxE+aZEYoBdjqWvLKL-4Odow@mail.gmail.com>

On Tue, Jul 13, 2021 at 10:30:48PM +0200, Hylke Hellinga wrote:
> Dear Alan,
> 
> Thank you.
> 
> I've just created the usbmon trace. It's fairly large due to it taking
> quite some time before the bug appears.
> I'm guessing it also has a lot of output due to the mouse moving x and
> y and me typing?
> 
> It can be viewed here:
> https://gist.github.com/Simbaclaws/70014d584d96dc0ac4920dffb1996583
> 
> Sorry for the somewhat late reply. Was helping someone on irc.
> 
> Please let me know if this can help debug the issue.

The usbmon trace contains a lot of -71 errors.  In general, errors of 
this type arise because the device's firmware has crashed (apparently 
not the case here, since the mouse continued to work okay), or because 
of interference caused by a bad cable or something similar.  Perhaps 
caused by the KVM switch itself.

The fact that the log says the mouse connected at full speed rather than 
high speed also indicates some sort of signal-related problem.

Have you tried doing an experiment where you plug the mouse directly 
into the computer rather than going through the switch?

Alan Stern

  reply	other threads:[~2021-07-14 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 18:19 ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller causing random full speed USB resets Hylke Hellinga
2021-07-13 18:42 ` Alan Stern
     [not found]   ` <CABUoX8sNbLuG0FB2_VtH14KhuBoRFB19a2V3cpgzdNDqiVUULA@mail.gmail.com>
     [not found]     ` <CABUoX8sT_=8aUdzhphwJXnRN2m_cKuJrDi1MtOrkaCTThT0wmA@mail.gmail.com>
2021-07-13 20:30       ` Hylke Hellinga
2021-07-14 14:54         ` Alan Stern [this message]
     [not found]           ` <CABUoX8uUhW4bdUZ6Roo=jEn=3UwUq2QVAMPcnyg8rbLzua09=w@mail.gmail.com>
2021-07-14 18:05             ` Alan Stern
     [not found]               ` <CABUoX8vWDRtr4hiVOEkT48=doG8xbAVD65Hve0QByLJpV0JsqQ@mail.gmail.com>
2021-07-14 18:19                 ` Hylke Hellinga
2021-07-14 19:02                   ` Hylke Hellinga
2021-07-14 19:52                     ` Alan Stern
2021-07-14 17:48 Hylke Hellinga

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=20210714145423.GB380727@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=hylke.hellinga@gmail.com \
    --cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.