Most curious. Based on what I read earlier, I was wondering about
the handling of the unlink watchdog during a known-dodgey path.
Specifically:
This "fires during a clean shutdown" path. If there's any way this
patch would affect resume handling, that's where I'd expect it to
kick in. Virtually nothing else *could* cause problems there.
If you'd like to experiment, modify the "if (...)" at the top of the
ehci_iaa_watchdog() function and make it just check to see if there's
an entry being reclaimed ... comment out the HC_IS_RUNNING() check.
FWIW the former has been confirmed as existing on some current AMD/ATI
chipsets (SB600 and SB700 are the numbers that come to mind).
--