On Tue, Jan 07, 2025 at 05:59:36PM +0200, Abel Vesa wrote: > On 25-01-07 16:19:26, Johan Hovold wrote: > > But I do indeed see something similar here on resume: > > > > [ 1891.737726] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0xe3f6ddbec0, fsynr=0x510000, cbfrsynra=0x14e0, cb=3 > > [ 1891.737738] arm-smmu 15000000.iommu: FSR = 00000402 [Format=2 TF], SID=0x14e0 > > [ 1891.737746] arm-smmu 15000000.iommu: FSYNR0 = 00510000 [S1CBNDX=81 PLVL=0] > > [ 1891.804342] r8152 7-1:1.0 eth0: carrier on > > [ 1902.039158] xhci-hcd xhci-hcd.1.auto: xHCI host not responding to stop endpoint command > > [ 1902.039191] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead > > [ 1902.039795] xhci-hcd xhci-hcd.1.auto: HC died; cleaning up > > [ 1902.040050] usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -5 > > [ 1902.040272] usb 1-1: PM: failed to resume async: error -5 > > [ 1902.581479] OOM killer enabled. > > [ 1902.586673] Restarting tasks ... > > [ 1902.587565] usb 1-1: USB disconnect, device number 2 > > Turns out it is the GDSC that has power status flags PWRSTS_OFF_ON when it > should've had PWRSTS_RET_ON. Sent a fix here: > > https://lore.kernel.org/all/20250107-x1e80100-clk-gcc-fix-usb2-gdsc-pwrsts-v1-1-e15d1a5e7d80@xxxxxxxxxx/ > > With this patch, the above resume issue goes away entirely. Indeed it does. Johan
