linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219532] Crash in RIP: 0010:xhci_handle_stopped_cmd_ring
Date: Tue, 26 Nov 2024 23:09:34 +0000	[thread overview]
Message-ID: <bug-219532-208809-8gVHeUXs1r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219532-208809@https.bugzilla.kernel.org/>

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

Michał Pecio (michal.pecio@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@gmail.com

--- Comment #5 from Michał Pecio (michal.pecio@gmail.com) ---
It looks like some device doesn't respond to address assignment after
connection. If you weren't connecting anything at the time, it's possible that
a device is buggy and had disconnected by itself a moment earlier, but the log
is too short to tell.

Not sure why it crashed. It looks like there were two attempts 6 seconds apart
and no crash on the first attempt.

It's unlikely that xhci was NULL near the end of the function. If it were,
there were several opportunities to crash earlier. The call to
xhci_mod_cmd_timer() in the next line dereferences xhci->cur_cmd, which is
perhaps more suspicious.

-- 
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:[~2024-11-26 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26  1:53 [Bug 219532] New: Crash in RIP: 0010:xhci_handle_stopped_cmd_ring bugzilla-daemon
2024-11-26  1:55 ` [Bug 219532] " bugzilla-daemon
2024-11-26  1:56 ` bugzilla-daemon
2024-11-26  2:00 ` bugzilla-daemon
2024-11-26  2:05 ` bugzilla-daemon
2024-11-26 23:09 ` bugzilla-daemon [this message]
2024-11-28  0:19 ` bugzilla-daemon
2024-12-01 22:06 ` bugzilla-daemon
2024-12-01 22:07 ` 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-219532-208809-8gVHeUXs1r@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;
as well as URLs for NNTP newsgroup(s).