[Bug 219532] Crash in RIP: 0010:xhci_handle_stopped_cmd_ring

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Michał Pecio (michal.pecio@xxxxxxxxx) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@xxxxxxxxx

--- Comment #5 from Michał Pecio (michal.pecio@xxxxxxxxx) ---
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.




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux