RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

test_suspend/6296 is trying to acquire lock:
 (hcd->bandwidth_mutex){+.+.+.}, at: [<ffffffff813cff38>] usb_reset_and_verify_device+0x2b8/0x760

but task is already holding lock:
 (&dev->pm_mutex/1){+.+...}, at: [<ffffffff813dca95>] usb_external_resume_device+0x35/0xa0

Version-Release number of selected component (if applicable):
RHEL6.3 debug kernel.

Steps to Reproduce:
1. Suspend to ram resume

Created attachment 612791 [details]
dmesg.txt

Hi Stanislaw,

I believe this was fixed in bz832126 and should be available in -310.el6 and later.

Let me know if that fixes it for you or not.

Cheers,
Don

Yes, no sign of warning on updated kernel.