From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214021] The USB devices fail to be detected during boot
Date: Mon, 16 Aug 2021 07:09:05 +0000 [thread overview]
Message-ID: <bug-214021-208809-ACKLPrq2Zu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214021-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214021
--- Comment #5 from Chris Chiu (chris.chiu@canonical.com) ---
I add printks to trace where the error happens. The dmesg show as down below
[ 44.488980] xhci_hcd 0000:00:14.0: FIXME: allocate a command ring segment
[ 44.488981] usb_alloc_dev: hcd driver alloc dev exist but return 0
[ 44.488982] usb usb1-port4: couldn't allocate usb_device
The first line show for the "xhci_dbg(xhci, "FIXME: allocate a command ring
segment\n");" in xhci_alloc_dev()
The second line shows the printk I add in usb_alloc_dev()
/* Root hubs aren't true devices, so don't allocate HCD resources */
if (usb_hcd->driver->alloc_dev && parent &&
!usb_hcd->driver->alloc_dev(usb_hcd, dev)) {
+ printk("%s: hcd driver alloc dev exist but return 0",
__func__);
usb_put_hcd(bus_to_hcd(bus));
kfree(dev);
return NULL;
}
The usb_hcd->driver->alloc_dev is equal to xhci_alloc_dev and fails the
xhci_queue_slot_control(). Does that mean anything regarding this?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-08-16 7:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 15:26 [Bug 214021] New: The USB devices fail to be detected during boot bugzilla-daemon
2021-08-10 15:27 ` [Bug 214021] " bugzilla-daemon
2021-08-10 15:39 ` bugzilla-daemon
2021-08-11 15:38 ` bugzilla-daemon
2021-08-12 2:31 ` bugzilla-daemon
2021-08-16 7:09 ` bugzilla-daemon [this message]
2021-08-16 7:29 ` bugzilla-daemon
2021-08-16 14:16 ` bugzilla-daemon
2021-08-18 5:48 ` bugzilla-daemon
2021-08-20 11:33 ` bugzilla-daemon
2021-08-20 14:31 ` bugzilla-daemon
2021-08-23 12:49 ` bugzilla-daemon
2021-08-23 14:06 ` bugzilla-daemon
2021-08-24 7:37 ` bugzilla-daemon
2021-08-25 12:08 ` bugzilla-daemon
2022-03-25 8:30 ` bugzilla-daemon
2022-04-07 21:25 ` bugzilla-daemon
2022-04-07 21:27 ` bugzilla-daemon
2022-04-08 11:55 ` bugzilla-daemon
2022-04-08 11:56 ` bugzilla-daemon
2022-04-08 11:57 ` bugzilla-daemon
2022-04-24 7:50 ` bugzilla-daemon
2022-04-24 7:52 ` bugzilla-daemon
2022-04-25 10:08 ` bugzilla-daemon
2022-04-25 11:00 ` bugzilla-daemon
2022-05-13 7:29 ` bugzilla-daemon
2022-05-13 8:29 ` 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-214021-208809-ACKLPrq2Zu@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 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.