On Mon, 1 Mar 2004, Martin Diehl wrote: > Arghhh - wait! While wondering why we have SETUP-CC==5 (DevNotResponding), > I've just realized the driver is trying to DMA to the stack during the > control-reads. That's definedly a bug and by luck it might be the > trigger. I'll fix this and repeat...
Ok, done that. This time I've even removed the hub so the stir4200 was the only usb-device (except root-hub of course) present in the system. Unfortunately the issue is still there. There seems to be a common pattern: the reportedly bad entry is always a SETUP packet with CC=5 and urb=NULL. And I'm wondering why it has DATA1, not DATA0! This time it was actually a control-write without data: ohci_hcd 0000:00:0c.1: bad entry 8414080 ohci_hcd 0000:00:0c.1: td_hash[1] ohci_hcd 0000:00:0c.1: entry td c8414040; urb c82ac934 index 0; hw next td 00000000 ohci_hcd 0000:00:0c.1: info 02140000 CC=0 DATA0 DI=0 IN R ohci_hcd 0000:00:0c.1: cbp 07220000 be 07220fff (len 4096) ohci_hcd 0000:00:0c.1: bad? td c8414080; urb 00000000 index 0; hw next td 08414040 ohci_hcd 0000:00:0c.1: info 5f000000 CC=5 DATA1 DI=0 SETUP ohci_hcd 0000:00:0c.1: cbp 00000000 be 00000000 (len 0) Given the same driver is working with ehci I'm starting to wonder whether it might be worth to check how ohci handles control transfers. But I'm not sure whether I understand the details there - Any ideas how to proceed? Martin ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
