public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218118] USB3 port does not work on Chromebook XE303C12 with Linux kernel 6.5.11
Date: Fri, 10 Nov 2023 14:37:49 +0000	[thread overview]
Message-ID: <bug-218118-208809-4SLSavAfL3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218118-208809@https.bugzilla.kernel.org/>

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

--- Comment #8 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
The debug output causes some latency, that could be one reason.

The log for example show that usb3 bus was just about to be suspended before it
detected something on the port:

[    2.337685] xhci-hcd xhci-hcd.6.auto: Get port status 3-1 read: 0x2a0,
return 0x100
[    2.337727] hub 3-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    2.337745] hub 3-0:1.0: hub_suspend
[    2.337769] usb usb3: bus auto-suspend, wakeup 1
[    2.337780] usb usb3: suspend raced with wakeup event
[    2.337786] usb usb3: usb auto-resume
[    2.376930] xhci-hcd xhci-hcd.6.auto: Port change event, 3-1, id 1, portsc:
0xa0206e1

-- 
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:[~2023-11-10 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 21:38 [Bug 218118] New: USB3 port does not work on Chromebook XE303C12 with Linux kernel 6.5.11 bugzilla-daemon
2023-11-09 14:52 ` [Bug 218118] " bugzilla-daemon
2023-11-09 19:06 ` bugzilla-daemon
2023-11-09 19:07 ` bugzilla-daemon
2023-11-09 19:10 ` bugzilla-daemon
2023-11-10  9:24 ` bugzilla-daemon
2023-11-10  9:26 ` bugzilla-daemon
2023-11-10  9:27 ` bugzilla-daemon
2023-11-10 14:37 ` 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-218118-208809-4SLSavAfL3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox