All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215649] all usb devices stop working and forced to reboot the system
Date: Thu, 27 Oct 2022 20:04:33 +0000	[thread overview]
Message-ID: <bug-215649-208809-CR0vMY3b1p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215649-208809@https.bugzilla.kernel.org/>

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

--- Comment #5 from Alan Stern (stern@rowland.harvard.edu) ---
Great!  Assuming that the 6.0 kernel works okay, you can consider the problem
fixed.  And it looks like I was wrong; this really was a software problem.

-- 
You may reply to this email to add a comment.

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

      parent reply	other threads:[~2022-10-27 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 15:08 [Bug 215649] New: all usb devices stop working and forced to reboot the system bugzilla-daemon
2022-03-01 15:18 ` [Bug 215649] " bugzilla-daemon
2022-03-01 16:21 ` bugzilla-daemon
2022-10-27  1:46 ` bugzilla-daemon
2022-10-27  5:58 ` bugzilla-daemon
2022-10-27 20:04 ` bugzilla-daemon [this message]

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-215649-208809-CR0vMY3b1p@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 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.