Bug 19652
Summary: | dib0700 - Remote no longer functional since release 2.6.34 | ||
---|---|---|---|
Product: | v4l-dvb | Reporter: | Michael Meier (michael.meier) |
Component: | dvb-usb | Assignee: | dvb-usb (v4l-dvb_dvb-usb) |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | alan, michael.meier |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.34 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Output of lsusb with receiver plugged in during boot
Output of lsusb after replugging receiver kernel config used for 2.6.36-rc6 |
Description
Michael Meier
2010-10-03 19:59:43 UTC
Today I noticed that the described error message "dib0700: rc submit urb failed" appears only if the receiver was already plugged in when the system boots up. usb_submit_urb is called with xfertype USB_ENDPOINT_XFER_INT in which it fails because interval==0. After replugging the receiver it correctly uses the xfertype USB_ENDPOINT_XFER_BULK and succeeds. Attached is the output of lsusb -v for both cases which clearly show different endpoint transfer types. This is the case no matter if the device was detected in cold or warm state, even with the dvb modules removed from the kernel completely, so the cause for this behavior lies somewhere else and is not directly related to commit 6a2071006b72bf887e38c025c60f98d2998ceacb. The device that is affected is a WinTV Nova TD (2040:9580) with dual tuner. I also tested this with a WinTV Nova T (2040:7070) with single tuner which is not behaving this way and working as usual. Created attachment 33022 [details]
Output of lsusb with receiver plugged in during boot
Created attachment 33032 [details]
Output of lsusb after replugging receiver
Created attachment 33042 [details]
kernel config used for 2.6.36-rc6
I just tested it with Windows and it seems like the behavior is the same. I started the system with the receiver plugged in and usbview from the Windows XP DDK lists the endpoint transfer type as "interrupt". After replugging the transfer type changes to "bulk". Does anyone know what could be the reason for this or can reproduce it on his hardware? |