On Fri, 23 Jun 2006, David Brownell wrote: > > > That's been said, but nonetheless the last few times I've tried to do > > > things like handling disconnect processing anything other than very > > > late (after khubd got woken up again), it was still deadlocksville. > > > Yes, this is _after_ folk have said "this has been fixed...". > > > > Okay, I have tried it. > > Hmm, when I tried that, I did it on suspend() paths not resume, and > the deadlocks were in PM core code. I didn't see that SCSI bug. > Maybe it really is fixed now. Unregistering child devices during suspend() also works okay. No deadlock. Mind you, trying to unregister a device from within its _own_ suspend method is guaranteed to deadlock. But that should already be obvious. Alan Stern
