Hi, On 03/29/2016 05:17 PM, Lipengcheng wrote: > Hi > Thanks Baolu very much! > Because of the reason usb3 module can not be used, it will affect the > strong of usb3 module; > 1, the xhci control is suspend and resume, why to re-allocate memory?
Some controllers need to set XHCI_RESET_ON_RESUME quirk. With this quirk bit set, host will be reset and reinitialized during resuming. > 2, whether we can allocate memory for more times, so we can avoid the > problem; Sorry. I didn't get your point. Best regards, Baolu > > Best Regards, > Pengcheng Li > > >> -----Original Message----- >> From: Lu Baolu [mailto:baolu...@linux.intel.com] >> Sent: Friday, March 25, 2016 10:19 PM >> To: Lipengcheng; Mathias Nyman; gre...@linuxfoundation.org >> Cc: st...@rowland.harvard.edu; ba...@ti.com; chasemetzge...@gmail.com; >> mj...@coreos.com; kbo...@gmail.com; jun...@freescale.com; >> robert.schlabb...@gmx.net; linux-usb@vger.kernel.org >> Subject: Re: 答复: 答复: 答复: 答复: 【xhci】suspend and resume core dump problem >> >> Hi, >> >> On 03/25/2016 03:39 PM, Lipengcheng wrote: >>> Hi, >>> Thanks Baolu very much! >>> The kernel is 3.10.Before the problem is inevitable emergence. But we >>> fix patch number:b630d4b9d05ba2e66878ca4614946d0f950d4111 >> and your suggest. >>> Then we resume and suspend the seventh and it is ok only if the usb3 can >>> not work. So the changes are effective. >> Thanks for testing. >> >>> In the wrong state which the usb3 can not work, we continue to suspend >>> and resume. It will be core dump. Should it be a normal >> phenomenon? >> >> dpm_run_callback(): platform_pm_resume+0x0/0x5c returns -12 >> PM: Device hiusb-xhci.0 failed to resume: error -12 >> >> >> Your xHCI host controller failed to resume. As the result, your usb3 devices >> should not work. You couldn't suspend it once more either. >> >> Best Regards, >> Baolu -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
