Comment 4 for bug 1694199

Hi Joe and thanks for your email.

I had not used this TV tuner on my desktop computer with an earlier
version of OS.

I had used the tuner (as stated earlier) on my laptop which used Ubuntu
16.04 and that was successful. So tuner OK.

At this point I am reluctant to venture to use the upstream kernel (my
lack of skills etc).

However what I did do was install Ubuntu 16.04 (linux 4.4.0-78-generic)
as a VM on my desktop. I have included the pertinent "dmesg" output
below. To my way of thinking, processing got beyond the issue I raised
(Unknown symbols) and the TV Tuner was identified. There is another
issue present

"[ 101.325099] dvb-usb: could not restart the USB controller CPU."

but I would be thinking that it is related to the VM setup.
Perhaps,because the host OS is not doing what it should do for the USB
TV Tuner, the guest OS stumbles). Subsequent to testing on VM, I checked
the TV Tuner on the laptop and it is functioning A OK.

Would you consider that this is sufficient to indicate that there was a
kernel bug?

Cheers

Jack

DMESG OUTPUT

usb 1-1: new high-speed USB devic[ 101.325099]e number 2 using ehci-pci
[ 97.883850] usb 1-1: New USB device found, idVendor=2040, idProduct=9300
[ 97.883853] usb 1-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 99.808439] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in cold
state, will try to load a firmware
[ 99.867024] dvb-usb: downloading firmware from file
'dvb-usb-nova-t-usb2-02.fw'
[ 101.325099] dvb-usb: could not restart the USB controller CPU.
[ 101.325115] dvb_usb_nova_t_usb2: probe of 1-1:1.0 failed with error -22
[ 101.325472] usbcore: registered new interface driver dvb_usb_nova_t_usb2
[ 101.330946] usb 1-1: USB disconnect, device number 2
[ 111.766837] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 111.917878] usb 1-1: New USB device found, idVendor=2040, idProduct=9301
[ 111.917888] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 111.917894] usb 1-1: Product: SOHO-FX2
[ 111.917898] usb 1-1: Manufacturer: Hauppau⁧攀
[ 111.917902] usb 1-1: SerialNumber: 9301-00-FXXXXXXX
[ 111.922917] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state.
[ 111.925455] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 111.929056] DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2)
[ 111.943336] dvb-usb: MAC address: XX:XX:XX:XX:XX:XX
[ 111.957735] usb 1-1: DVB: registering adapter 0 frontend 0 (DiBcom
3000MC/P)...
[ 112.172674] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:0b.0/usb1/1-1/input/input8
[ 112.173027] dvb-usb: schedule remote query interval to 100 msecs.
[ 112.173037] dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully
initialized and connected.
[ 114.269804] dvb-usb: recv bulk message failed: -110

On 31/05/17 01:11, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.12 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>