Re: Autosuspend and unbound interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On May 5, 2010, at 12:03 PM, Alan Stern wrote:

>> May  5 11:34:00 localhost kernel: usb 3-3: usb_autoresume_device: cnt 1 -> 1
>> May  5 11:34:00 localhost kernel: usb 3-3: usb_autosuspend_device: cnt 0 -> -16
>
> These -EBUSY error codes indicate that the usage_count for one of the
> interfaces is nonzero.  (Well, it could be something else, like the
> child_count, but most likely it's the usage_count.)

It appears that usb_autosuspend_device() is returning -EBUSY because
__pm_runtime_idle() sees !pm_children_suspended().

The child_count is 1, and ignore_children is 0.

> Add some debugging
> statements to the non-is_usb_device cases in usb_runtime_*(); you may
> find out which and why.

Rob.

The information and any attached documents contained in this message
may be confidential and/or legally privileged.  The message is
intended solely for the addressee(s).  If you are not the intended
recipient, you are hereby notified that any use, dissemination, or
reproduction is strictly prohibited and may be unlawful.  If you are
not the intended recipient, please contact the sender immediately by
return e-mail and destroy all copies of the original message.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux