Hi, I need some help debugging a USB transfer problem on my raspberry pi. I know this is not a mainstream kernel issue but I would be glad if someone here can help me understand and debug the problem. The problem is that the DVB Transport stream recorded from a usb DVB stick (cinergy htc stick) attached to a usb hub which is attached to the raspberry pi is broken. I use the latest media_build from linuxtv.org against a 3.1.9 raspberry pi kernel. The same drivers from the media_build work perfectly with a 3.1.9 kernel on my thinkpad. [ 126.162705] tda18271: performing RF tracking filter calibration [ 128.056572] tda18271: RF tracking filter calibration complete [ 128.057855] em28xx #0/2-dvb: Using 5 buffers each with 64 x 940 bytes [ 129.052712] em28xx #0/2-dvb: ISO ERROR COUNT: 1. [ 129.052743] em28xx #0/2-dvb: URB packet 0, status -4001 [Unknown]. [ 129.581352] em28xx #0/2-dvb: ISO ERROR COUNT: 1. [ 129.581384] em28xx #0/2-dvb: URB packet 0, status -4001 [Unknown]. [ 129.872090] em28xx #0/2-dvb: ISO ERROR COUNT: 1. [ 129.872122] em28xx #0/2-dvb: URB packet 0, status -4001 [Unknown]. [ 129.969224] em28xx #0/2-dvb: ISO ERROR COUNT: 1. [ 129.969258] em28xx #0/2-dvb: URB packet 44, status -4001 [Unknown]. My assumption is that the isochronous transfer is broken for the usb host driver. The error code is defined in: drivers/usb/host/dwc_common_port/dwc_os.h:#define DWC_E_NO_STREAM_RES 4001 which is caused by a DWC_OTG_HC_XFER_FRAME_OVERRUN in the URB: dwc_otg/dwc_otg_hcd_intr.c:753: frame_desc->status = -DWC_E_NO_STREAM_RES; I'm a bit lost since I do not have any USB specific knowledge but I really want to get the DVB Stick running ;) Is there anything you recommend me to check/test/read? What can I test/check? Is there a test tool for testing the isochronous transfer for a host? (I looked at the usbtest driver in the kernel, but I can't figure out how to test isochronous transfer with it) Thanks for your help! Cheers, Ruben -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
