WinTV DualHD + Kernel 4.8.0 + Plex 1.7.2.3878-8088811b8

General Discussions Plex Features
1

I’ve attempted to include as much debugging/troubleshooting information as possible, please let me know what other information you might need to diagnose the problem.

The kernel sees the device without issue but when attempting to use the device I get a kernel stack trace.

These instructions were followed (in the “Plex and Hauppauge tuners” tab of the documentation):
http://www.hauppauge.com/site/support/linux.html and https://github.com/b-rad-ndi/ubuntu-media-tree-kernel-builder
(basically, add haupuage apt-repository, apt-get update, apt-get install linux-image-mediatree linux-headers-mediatree)

Jun 3 15:30:51 hostname kernel: [ 846.879919] INFO: task Plex Tuner Serv:2690 blocked for more than 120 seconds.
Jun 3 15:30:51 hostname kernel: [ 846.879952] Not tainted 4.8.0-53201705311620-generic #0+mediatree+hauppauge-Ubuntu
Jun 3 15:30:51 hostname kernel: [ 846.880000] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
Jun 3 15:30:51 hostname kernel: [ 846.880048] Plex Tuner Serv D ffff8aa9e3633cf0 0 2690 2338 0x00000000
Jun 3 15:30:51 hostname kernel: [ 846.880052] ffff8aa9e3633cf0 00ff8aaa28371000 ffff8aaa30fa5e80 ffff8aa9f7d73600
Jun 3 15:30:51 hostname kernel: [ 846.880053] ffff8aa9e3633cd0 ffff8aa9e3634000 ffffffffa94e9f30 ffff8aaa2da3dc28
Jun 3 15:30:51 hostname kernel: [ 846.880055] ffffb843c1fa3000 ffff8aaa2bec3ec0 ffff8aa9e3633d08 ffffffffa8e9adc5
Jun 3 15:30:51 hostname kernel: [ 846.880056] Call Trace:
Jun 3 15:30:51 hostname kernel: [ 846.880062] [] schedule+0x35/0x80
Jun 3 15:30:51 hostname kernel: [ 846.880064] [] usb_kill_urb+0x98/0xd0
Jun 3 15:30:51 hostname kernel: [ 846.880067] [] ? wake_atomic_t_function+0x60/0x60
Jun 3 15:30:51 hostname kernel: [ 846.880071] [] em28xx_stop_urbs+0x2e/0xb0 [em28xx]
Jun 3 15:30:51 hostname kernel: [ 846.880075] [] em28xx_stop_feed+0x38/0x50 [em28xx_dvb]
Jun 3 15:30:51 hostname kernel: [ 846.880082] [] dmx_ts_feed_stop_filtering+0x4b/0xb0 [dvb_core]
Jun 3 15:30:51 hostname kernel: [ 846.880087] [] dvb_dmxdev_feed_stop+0x6d/0xb0 [dvb_core]
Jun 3 15:30:51 hostname kernel: [ 846.880091] [] dvb_dmxdev_filter_stop+0x31/0xc0 [dvb_core]
Jun 3 15:30:51 hostname kernel: [ 846.880094] [] dvb_demux_release+0x48/0x1a0 [dvb_core]
Jun 3 15:30:51 hostname kernel: [ 846.880096] [] __fput+0xe7/0x230
Jun 3 15:30:51 hostname kernel: [ 846.880097] [] ____fput+0xe/0x10
Jun 3 15:30:51 hostname kernel: [ 846.880099] [] task_work_run+0x80/0xa0
Jun 3 15:30:51 hostname kernel: [ 846.880101] [] exit_to_usermode_loop+0xc2/0xd0
Jun 3 15:30:51 hostname kernel: [ 846.880102] [] syscall_return_slowpath+0x4e/0x60
Jun 3 15:30:51 hostname kernel: [ 846.880103] [] entry_SYSCALL_64_fastpath+0xa6/0xa8

Additionally, when doing lsusb a kernel error is emitted:
$ sudo lsusb -v -d 2040:026d 1>/dev/null
Jun 3 15:45:59 hostname kernel: [ 1754.935479] lgdt3306a: error (addr 0e reg 0080 error (ret == -110)

Additionally, just trying a basic scan from the command line doesn’t seem to work.
$ w_scan -fa -A1 -c US -X -C UTF-8
w_scan -fa -A1 -c US -X -C UTF-8
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for UNITED STATES
ATSC
VSB US/CA, DVB-T TW
scan type TERRCABLE_ATSC, channellist 1
output format czap/tzap/szap/xine
output charset ‘UTF-8’
Info: using DVB adapter auto detection.
main:3904: FATAL: ***** NO USEABLE TERRCABLE_ATSC CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.

Possibly related loaded kernel modules
$ lsmod | egrep -i dvb|em2|hau|tv|dvr|video|v4l
rc_hauppauge 16384 0
em28xx_rc 20480 0
rc_core 40960 4 rc_hauppauge,em28xx_rc
em28xx_dvb 36864 2
dvb_core 126976 1 em28xx_dvb
em28xx 94208 2 em28xx_rc,em28xx_dvb
tveeprom 24576 1 em28xx
v4l2_common 16384 1 em28xx
videodev 184320 1 v4l2_common
media 40960 3 videodev,em28xx,si2157

PCI devices:
$ sudo lsusb -v -d 2040:026d
Bus 001 Device 002: ID 2040:026d Hauppauge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0x026d
bcdDevice 1.00
iManufacturer 3 HCW
iProduct 1 955D
iSerial 2 0013861204
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 55
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1 [13/2533]
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

2

YUP. Version 1.7.2.3878 is dvr mess…

3

Please report this to Hauppauge, since you’re having an issue with their kernel.

4

@keithah said:
Please report this to Hauppauge, since you’re having an issue with their kernel.

Thanks… Went there before I came here. I’ll forward any relevant information received here for community benefit - same reason I posted here after contacting Hauppauge.

5

Thanks! Just making sure they know. Unfortunately the guy who built those kernel packages is on an extended vacation, so not sure when he’ll be back.

6

Hello again -

I received a second reply from Hauppage, which I’ve added to my thread here:

After my 2nd exchange with Hauppage, I am less convinced it is the same problem as described in this thread, as in your post, w_scan output actually fails to see the device at all (“main:3904: FATAL: ***** NO USEABLE TERRCABLE_ATSC CARD FOUND. *****”), whereas in my case w_scan sees the device but finds no channels (now I’ve given my default user the appropriate video group permissions). See the w_scan output file attached to the recent post in my thread for what I receive.

Sorry, I know this doesn’t help you at all! Just wanted to note in case others with a problem more like mine are reading this thread. Hope we both get it working eventually!

cheers

Paul

7

Hey @neonwombat , I’m similarly in the same situation as you where w_scan finds no channels even though the device is functioning correctly. I’m (losing patience) patiently awaiting responses from Hauppauge. My next step might be to return the WinTV device for a refund… I’m attaching my w_scan log as well as my output seems slightly different than your output.

8

Hi @stgarf , thanks for your reply. Sorry to hear you’re still having trouble. And thanks for your w_scan output - it appears like yours is getting further than mine in that you have some “signal ok” messages! But then it seems to fail later in the process with the “tune to” statements :frowning:

I’ve never seen a successful w_scan output so I don’t know what it should look like. Additionally, I’m scanning DVB-T/T2, not ATSC like you, so no idea if mine would look the same as yours even if successful.

Good luck with it! I’ve passed the point at which I can return this so might need to offload it to my brother who uses Windows and get a HDHomeRun, or give up on the idea of Live TV / DVR in Plex. If I get any further I’ll post info here.

9

@stgarf - an update from me. I found a solution that worked for me - see my post here. Not sure if it will help in your situation but wanted to let you know just in case.