Well, from the look of things it's probably broken by the hid2hci udev rule for S3 resume. To make sure (and to figure out how we can fix it); could you please attach the output of the udev log and reproduce a suspend/resume cycle?
To get the udev logs:
/sbin/udevadm monitor
This will show all udev events in output, until killed of with Control-C or something, so it will log things across a suspend/resume.
Well, from the look of things it's probably broken by the hid2hci udev rule for S3 resume. To make sure (and to figure out how we can fix it); could you please attach the output of the udev log and reproduce a suspend/resume cycle?
To get the udev logs:
/sbin/udevadm monitor
This will show all udev events in output, until killed of with Control-C or something, so it will log things across a suspend/resume.
Thanks in advance!