APM suspend/resume & USB trouble, 5.2-R, Toshiba Sat Pro 6100

[G.E. Rafe]

An update to my previous observations regarding APM on my
Toshiba Satellite Pro 6100 with 5.2-R.
Since that post, I'm finding that USB isn't surviving across
multiple suspend/resume cycles while running 5.2-R;
this behavior with the most recent updates to src/sys/dev/usb ...

Kernel messages following *first* suspend/resume cycle:

usbd_new_device bus=0xc4777000 port=1 depth=1 speed=2
usbd_new_device: adding unit addr=2, rev=110, class=9, subclass=0, protocol=0, maxpacket=8, len=18, speed=2
usbd_new_device: new dev (addr 2), dev=0xc4723400, parent=0xc4723900
usbd_probe_and_attach: trying device specific drivers
uhub1: Atmel Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2
usbd_set_config_index: status=0x0000, error=NORMAL_COMPLETION
usbd_set_config_index: (addr 1) cno=2 attr=0xe0, selfpowered=0, power=64
usbd_set_config_index: set config 1
uhub1: 4 ports with 4 removable, bus powered
usbd_new_device bus=0xc4777000 port=4 depth=2 speed=1
usbd_new_device: adding unit addr=3, rev=200, class=0, subclass=0, protocol=0, maxpacket=8, len=18, speed=1
usbd_new_device: new dev (addr 3), dev=0xc4b6dc80, parent=0xc4723480
usbd_probe_and_attach: trying device specific drivers
usbd_probe_and_attach: no device specific driver found
usbd_probe_and_attach: looping over 1 configurations
usbd_set_config_index: (addr 1) cno=3 attr=0xa0, selfpowered=0, power=98
usbd_set_config_index: set config 1
ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 3, iclass 3/1
ums0: 3 buttons and Z dir.

And all is well, until the *second* suspend/resume cycle:

usbd_new_device bus=0xc4777000 port=1 depth=1 speed=2
usbd_new_device: addr=2, getting first desc failed
usbd_remove_device: 0xc4b86a00
uhub_explore: usb_new_device failed, error=TIMEOUT
uhub0: device problem, disabling port 1

Ugh, no more USB devices (read, mouse)
[hurrah for the dimple in the keyboard].

OK, so I'm back to my suspend/resume-reliable 4.9-R partition,
from where I compose this post.

Looking forward to seeing a fix for this.
--
Gary E. RAFE, Ph.D.
rafege at mail.com