OK, here's the result of the bisection: ef513be0a9057cc6baf5d29566aaaefa214ba344 is the first bad commit commit ef513be0a9057cc6baf5d29566aaaefa214ba344 Author: Jim Lin <jilin@xxxxxxxxxx> Date:???? Mon Jun 3 18:53:44 2019 +0800 ?????? usb: xhci: Add Clear_TT_Buffer ?????? ?????? USB 2.0 specification chapter 11.17.5 says "as part of endpoint halt ?????? processing for full-/low-speed endpoints connected via a TT, the host ?????? software must use the Clear_TT_Buffer request to the TT to ensure ?????? that the buffer is not in the busy state". ?????? ?????? In our case, a full-speed speaker (ConferenceCam) is behind a high- ?????? speed hub (ConferenceCam Connect), sometimes once we get STALL on a ?????? request we may continue to get STALL with the folllowing requests, ?????? like Set_Interface. ?????? ?????? Here we invoke usb_hub_clear_tt_buffer() to send Clear_TT_Buffer ?????? request to the hub of the device for the following Set_Interface ?????? requests to the device to get ACK successfully. ?????? ?????? Signed-off-by: Jim Lin <jilin@xxxxxxxxxx> ?????? Acked-by: Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> ?????? Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> ??drivers/usb/host/xhci-ring.c | 27 ++++++++++++++++++++++++++- ??drivers/usb/host/xhci.c?????????? | 21 +++++++++++++++++++++ ??drivers/usb/host/xhci.h?????????? |?? 5 +++++ ??3 files changed, 52 insertions(+), 1 deletion(-) On 7/27/19 6:59 AM, Greg KH wrote: > On Fri, Jul 26, 2019 at 11:15:46PM -0400, Bob Gleitsmann wrote: >> Hello, >> >> >> I have seen kernel oopses on waking from suspend to memory. I got this >> twice, one dmesg with backtrace attached. The other one had the failure >> in the same place in the code. >> >> >> This is kernel 5.3.0-rc1, patched for another problem in ethernet PHY >> driver. Have not had the problem with earlier kernels. Using Gentoo >> linux, amd64, but git kernel. > Any chance you can run 'git bisect' to track down the offending commit? > > thanks, > > greg k-h >