All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216766] USB enumeration lockup
Date: Mon, 05 Dec 2022 18:34:34 +0000	[thread overview]
Message-ID: <bug-216766-208809-iMMAFcHlbm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216766-208809@https.bugzilla.kernel.org/>

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

--- Comment #9 from Jan Burgmeier (jan.burgmeier@gmx.de) ---
Hi Matthias,

thanks for your feedback. You are right I have also 2 Monitors connected to the
docking station.

I enabled the logging and tried to reproduce the error. The behavior seems to
be a bit different, the error seems to happen a bit less but after resuming
when reconnecting the docking station I need to connect it twice on the first
connect the monitors are not recognized.

After some tries I was able to reproduce the error, multiple suspend and
resumes where needed, it seems that a longer suspend time increases the chance
to get the error:
>> https://bugzilla.kernel.org/attachment.cgi?id=303361

I had also one try which was even weirder, where the system seemed not to go
into suspend because the backlight stayed on but after ?resume? the error
occurred:
>> https://bugzilla.kernel.org/attachment.cgi?id=303360

-- 
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-12-05 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 18:54 [Bug 216766] New: USB enumeration lockup bugzilla-daemon
2022-12-02 20:27 ` [Bug 216766] " bugzilla-daemon
2022-12-02 21:09 ` bugzilla-daemon
2022-12-03  2:51 ` bugzilla-daemon
2022-12-03 14:32 ` bugzilla-daemon
2022-12-05 15:58 ` bugzilla-daemon
2022-12-05 16:06 ` bugzilla-daemon
2022-12-05 18:32 ` bugzilla-daemon
2022-12-05 18:33 ` bugzilla-daemon
2022-12-05 18:34 ` 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-216766-208809-iMMAFcHlbm@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.