Paul:

Okay, I think this patch ought to do the trick.  I modified the PM
suspend/resume code so that on buggy motherboards like yours the suspend
routine really does a reset, while on normal motherboards the resume
routine really does a resume.  I haven't tried that part out because,
truth to tell, I'm a little scared of doing an APM/ACPI suspend.  Not long
ago I walked away from my computer for about a half-hour, leaving 2.5.69
running.  When I got back the screen was blank and the machine was totally
non-responsive.

I changed the delays in reset_hc() to use schedule_timeout() rather than
wait_ms(), which should make it more friendly.

Finally, I put the USBCMD_FGR back into wakeup_hc().  The reason for it is
now evident: a wakeup might be the result of a system-initiated event
as opposed to something requested by a device.