Op woensdag 22-02-2012 om 20:48 uur [tijdzone -0500], schreef Kevin O'Connor:
OHCI init on dev 00:0f.4 (regs=0xfe00e000) pmm_malloc zone=0x1f7bfec4 handle=ffffffff size=256 align=100 ret=0x1f7cff00 (detail=0x1f7b7000) pmm_malloc zone=0x1f7bfec4 handle=ffffffff size=16 align=10 ret=0x1f7cfef0 (detail=0x1f7b6fd0) ohci init: c=97 h=0x1f7cff00 h=1f7cff00 f=0
ohci wait: c=87 h=0x1f7cff00 f=236 WARNING - Timeout at ohci_waittick:134!
That's odd. It looks like the controller was running for 236ms and then freezes. The only thing I can think of to track this down is to sprinkle dprintf() statements through the code until we find what caused the controller to stop.
As an example of more debugging, see the patch below. I think you'll likely need to keep adding statements until finding the place where the counter stops.
Another thing to check is to see if the Linux code has any quirks for this particular controller.
I ran your debugging example with timestamps enabled. (attached for reference) I'l try to study/test this some more in the next day's.
Thanks for your help!