linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.
Date: Mon, 28 Sep 2020 18:22:28 +0000	[thread overview]
Message-ID: <bug-209137-208809-NoDqmBqFTE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209137-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #6 from Alan Stern (stern@rowland.harvard.edu) ---
You should be more careful about what you write.  In the original bug
description you said that USB isn't working, but in comment #5 you said that
USB isn't the problem.  Try to be more consistent.

Your dmesg log from the 5.4 kernel does show some errors from the HID driver. 
You should collect a similar dmesg log under a 5.0 kernel for comparison.

Another thing that would help is the output from running as superuser "lsusb
-v" for the Logitech receiver.  Under either 5.0 or 5.4, the output should be
the same.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-28 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-209137-208809@https.bugzilla.kernel.org/>
2020-09-28  9:09 ` [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working bugzilla-daemon
2020-09-28 18:22 ` bugzilla-daemon [this message]
2020-09-28 20:30 ` bugzilla-daemon
2020-10-07  7:29 ` bugzilla-daemon
2020-10-07 20:29 ` bugzilla-daemon
2020-10-07 20:37 ` bugzilla-daemon
2020-10-08 14:35   ` Alan Stern
2020-10-09  8:31     ` Benjamin Tissoires
2020-10-08 14:35 ` bugzilla-daemon
2020-10-08 16:44 ` bugzilla-daemon
2020-10-09  8:37 ` bugzilla-daemon

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=bug-209137-208809-NoDqmBqFTE@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 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).