kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jorge Fernandez Monteagudo <jorgefm@cirsa.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: USB resets
Date: Tue, 20 Apr 2021 09:22:43 +0200	[thread overview]
Message-ID: <YH6BQ8spag0VHn/m@kroah.com> (raw)
In-Reply-To: <DB9PR10MB45226EE711E53D59D4E98AAAA1489@DB9PR10MB4522.EURPRD10.PROD.OUTLOOK.COM>

On Tue, Apr 20, 2021 at 07:17:10AM +0000, Jorge Fernandez Monteagudo wrote:
> Hi all,
> 
> I'm using an ancient 4.17.1 kernel and I'm seeing an weird USB behavior. A touchscreen device is been detected and disconnected in a 4 seconds pattern.
> 
> # dmesg | grep 1.3.2[    2.170041] usb 1-1.3.2: new full-speed USB device number 6 using ehci-pci
> [    2.254868] input: Silicon Works Multi-touch SW4101C as /devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.3/1-1.3.2/1-1.3.2:1.0/0003:29BD:4101.0001/input/input2
> [    2.254958] hid-multitouch 0003:29BD:4101.0001: input: USB HID v1.00 Mouse [Silicon Works Multi-touch SW4101C] on usb-0000:00:12.0-1.3.2/input0
> [    6.776320] usb 1-1.3.2: USB disconnect, device number 6

Bad hardware, the kernel can not cause a disconnect :(

Do you have a flaky cable or underpowerd hub here?

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-04-20  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  7:17 USB resets Jorge Fernandez Monteagudo
2021-04-20  7:22 ` Greg KH [this message]
2021-04-20  7:41   ` Jorge Fernandez Monteagudo
2021-04-20  8:52     ` Greg KH
2021-04-22  7:32       ` Jorge Fernandez Monteagudo
2021-04-22  8:03         ` Greg KH

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=YH6BQ8spag0VHn/m@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jorgefm@cirsa.com \
    --cc=kernelnewbies@kernelnewbies.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).