Re: lockdep report at resume

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

On Wed, 2009-02-11 at 13:03 +0100, Jiri Kosina wrote:

> OK, so we are calling usb_reset_device() from hid_reset() workqueue. You 
> have a composite device, mouse interface being handled by bcm5974 driver, 
> and keyboard interface being handled by usbhid driver.
> 
> bcm5974 driver doesn't have _pre_reset() and _post_reset() callbacks, so 
> full unbind/bind cycle is performed by USB core. bcm5974_disconnect() 
> calls input_unregister_device(), which creates reset_work -> 
> input_dev->mutex dependency.
> 
> Unfortunately I don't seem to see from the lockdep dumps where does the 
> input_dev->mutex -> reset_work dependency come from, am I just completely 
> blind?

Any news on this? I just got it again on -rc5, entirely the same report,
though it seems I need to have a mouse plugged in, then hibernate,  then
unplug mouse and finally resume to get this report. IOW it doesn't seem
to happen if I don't change the hid devices during hibernate.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]