Bug 193901

Summary:	dvb-usb: bulk message failed on Linux 4.9 - on Linux 4.8 no issues
Product:	Drivers	Reporter:	Francois (francois5537)
Component:	USB	Assignee:	Greg Kroah-Hartman (greg)
Status:	RESOLVED CODE_FIX
Severity:	blocking
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	4.9.7	Subsystem:
Regression:	No	Bisected commit-id:

Description Francois 2017-02-03 19:22:15 UTC

Using Mygica T230 on Linux 4.9.7:
[ 1948.418802] usb 1-1: USB disconnect, device number 6
[ 1948.455998] dvb-usb: Mygica T230 DVB-T/T2/C successfully deinitialized and disconnected.
[ 1950.636574] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[ 1950.770804] usb 1-1: language id specifier not provided by device, defaulting to English
[ 1950.773837] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 1950.909942] dvb-usb: recv bulk message failed: -11
[ 1951.016674] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1951.016920] DVB: registering new adapter (Mygica T230 DVB-T/T2/C)
[ 1951.021056] dvb-usb: recv bulk message failed: -11
[ 1951.021071] si2168: probe of 10-0064 failed with error -121
[ 1951.021077] dvb-usb: no frontend was attached by 'Mygica T230 DVB-T/T2/C'
[ 1951.021316] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-1/input/input29
[ 1951.021687] dvb-usb: schedule remote query interval to 100 msecs.

Switching back to Linux 4.8.13 results in a working USB-DVB, and the error/warning message don't show up.

The configs are the same, so it seems a issue with the module(s) (si2168?).
Thanks!

Comment 1 Greg Kroah-Hartman 2017-02-03 20:46:08 UTC

On Fri, Feb 03, 2017 at 07:22:15PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=193901
> 
>             Bug ID: 193901
>            Summary: dvb-usb: bulk message failed on Linux 4.9 - on Linux
>                     4.8 no issues

All USB bugs should be sent to the linux-usb@vger.kernel.org mailing
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release.

Comment 2 Francois 2017-05-25 08:56:30 UTC

Fixed on 4.11.