On 18.08.2016 09:27, Felipe Balbi wrote:
Hi,
Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes:
On Wed, Aug 17, 2016 at 09:56:02PM +0200, Filip Ayazi wrote:
Forwarding bug report from bugzilla #153211 as requested:
System crashes completely during or immediately after installing APK to android
phone over usb using android studio. I was unable to reproduce this bug any
other way.
So the crash is on the host device, or the gadget device (the phone)?
Seems like host side gets stuck :-)
The only way to recover after the crash is a hard restart, netconsole captures
the following at the time:
[10592.718753] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [java:18908]
[10620.720015] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [java:18908]
[10648.721278] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10676.722541] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10704.723804] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10732.725067] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10760.726330] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10788.727594] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10816.728857] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
[10844.730120] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [java:18908]
Bisecting shown that commit
86065c2719 "xhci: don't rely on precalculated value of needed trbs in the enqueue loop"
somehow introduced the issue, but I can't find how.
Please let me know how I can help to fix this.
Can you test this commit?
https://git.kernel.org/cgit/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus&id=5be1233bacedbeb166c4f7a8136c03cec18bf1ee
It's a patch mentioning the same situation
The patch is in Greg's usb-linus branch, and on it's way to Linus tree.
0d2daad xhci: really enqueue zero length TRBs.
-Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
