Re: USB suspend/resume race

2014-05-29 Thread Martin Pieuchot
On 19/01/10(Tue) 01:07, Jean-Philippe Ouellet wrote: On 26/05/14(Mon) 13:46, Martin Pieuchot wrote: I'd appreciate if people having troubles with suspend/resume could try this diff an report back. Fixes it for me! :D Many thanks. You're welcome. Previous diff was lacking the header

Re: USB suspend/resume race

2014-05-28 Thread Jean-Philippe Ouellet
On 26/05/14(Mon) 13:46, Martin Pieuchot wrote: I'd appreciate if people having troubles with suspend/resume could try this diff an report back. Fixes it for me! :D Many thanks. Previous diff was lacking the header chunk, please use this one instead. Was the corresponding commit missing the

USB suspend/resume race

2014-05-26 Thread Martin Pieuchot
It is currently possible to trigger a race between the thread doing DVACT_QUIESCE and the USB thread exploring the buses. This race is really easy to reproduce if you have a lot of controllers and you try to suspend just after resuming. In the best case, it blows your kernel during suspend, in

Re: USB suspend/resume race

2014-05-26 Thread Martin Pieuchot
On 26/05/14(Mon) 13:46, Martin Pieuchot wrote: It is currently possible to trigger a race between the thread doing DVACT_QUIESCE and the USB thread exploring the buses. This race is really easy to reproduce if you have a lot of controllers and you try to suspend just after resuming. In the

Re: USB suspend/resume race

2014-05-26 Thread Mattieu Baptiste
On Mon, May 26, 2014 at 1:51 PM, Martin Pieuchot mpieuc...@nolizard.orgwrote: On 26/05/14(Mon) 13:46, Martin Pieuchot wrote: It is currently possible to trigger a race between the thread doing DVACT_QUIESCE and the USB thread exploring the buses. This race is really easy to reproduce if