Arch Linux

replabrobin

Member

Registered: 2010-05-06

Posts: 234

[SOLVED] Intel NUC using second dvb-t device causes usb lockup

I have an intel NUC D54250WYK running latest non-testing arch.

linux minikat 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64 GNU/Linux

I have two PCTV 290e cards.

Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 009: ID 2013:024f PCTV Systems nanoStick T2 290e
Bus 002 Device 008: ID 2013:024f PCTV Systems nanoStick T2 290e
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 007: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 002 Device 010: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 006: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 002 Device 005: ID 9e88:9e8f  
Bus 002 Device 004: ID 1e4e:0110 Cubeternet 
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Both of these work fine running alone (ie using just /dev/dvb/adapter0 or adapter1). However, when I run both together all my usb devices seem to disappear. Using the power button I can shut the system down. In the logs I see this

Nov 17 22:42:44 minikat kernel: tda18271: performing RF tracking filter calibration
Nov 17 22:42:46 minikat kernel: tda18271: RF tracking filter calibration complete
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command.
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: Assuming host is dying, halting host. 
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 17 22:42:51 minikat kernel: usb 1-3: USB disconnect, device number 2
Nov 17 22:42:51 minikat kernel: usb 1-3.1: USB disconnect, device number 4
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-5)
Nov 17 22:42:51 minikat kernel: i2c i2c-11: cxd2820r: i2c rd failed=-5 reg=db len=1
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xc0 failed (error=-19)
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-19)
Nov 17 22:42:51 minikat kernel: i2c i2c-11: cxd2820r: i2c rd failed=-19 reg=db len=1
Nov 17 22:42:51 minikat kernel: __tda18271_write_regs: [11-0060|M] ERROR: idx = 0x5, len = 1, i2c_transfer returned: -19
Nov 17 22:42:51 minikat kernel: tda18271_set_params: [11-0060|M] error -19 on line 985
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-19)
......

searching reveals a similar problem here https://bugs.launchpad.net/ubuntu/+sour … ug/1306712.

It doesn't seem to matter which device is used second or which application is using them; ie 2 x vlc or vlc + tzap etc etc all seem to cause the problem.

I used the same devices on my old acer revo 3610 and they work fine together there.

I would like to report this to Intel if I can get the right information together. Is there something I can do to clarify the problem?

Edit: added relevant device stuff from the same boot

Nov 17 22:40:35 minikat kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Nov 17 22:40:35 minikat kernel: em28xx: DVB interface 0 found: isoc
Nov 17 22:40:35 minikat kernel: em28xx: chip ID is em28174
Nov 17 22:40:36 minikat kernel: em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x924125c8
Nov 17 22:40:36 minikat kernel: em28174 #0: EEPROM info:
Nov 17 22:40:36 minikat kernel: em28174 #0:     microcode start address = 0x0004, boot configuration = 0x01
Nov 17 22:40:36 minikat kernel: em28174 #0:     No audio on board.
Nov 17 22:40:36 minikat kernel: em28174 #0:     500mA max power
Nov 17 22:40:36 minikat kernel: em28174 #0:     Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Nov 17 22:40:36 minikat kernel: em28174 #0: Identified as PCTV nanoStick T2 290e (card=78)
Nov 17 22:40:36 minikat kernel: em28174 #0: dvb set to isoc mode.
Nov 17 22:40:36 minikat kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Nov 17 22:40:36 minikat kernel: em28xx: DVB interface 0 found: isoc
Nov 17 22:40:36 minikat kernel: em28xx: chip ID is em28174
Nov 17 22:40:36 minikat kernel: em28174 #1: EEPROM ID = 26 00 01 00, EEPROM hash = 0x9de637c6
Nov 17 22:40:36 minikat kernel: em28174 #1: EEPROM info:
Nov 17 22:40:36 minikat kernel: em28174 #1:     microcode start address = 0x0004, boot configuration = 0x01
Nov 17 22:40:36 minikat kernel: em28174 #1:     No audio on board.
Nov 17 22:40:36 minikat kernel: em28174 #1:     500mA max power
Nov 17 22:40:36 minikat kernel: em28174 #1:     Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Nov 17 22:40:36 minikat kernel: em28174 #1: Identified as PCTV nanoStick T2 290e (card=78)
Nov 17 22:40:36 minikat kernel: em28174 #1: dvb set to isoc mode.
Nov 17 22:40:36 minikat kernel: usbcore: registered new interface driver em28xx
Nov 17 22:40:36 minikat kernel: em28174 #0: Binding DVB extension
Nov 17 22:40:36 minikat kernel: DVB: registering new adapter (em28174 #0)
Nov 17 22:40:36 minikat kernel: em28174 #0: DVB extension successfully initialized
Nov 17 22:40:36 minikat kernel: em28174 #1: Binding DVB extension
Nov 17 22:40:36 minikat kernel: DVB: registering new adapter (em28174 #1)
Nov 17 22:40:36 minikat kernel: em28174 #1: DVB extension successfully initialized
Nov 17 22:40:36 minikat kernel: em28xx: Registered (Em28xx dvb Extension) extension
Nov 17 22:40:36 minikat kernel: em28174 #0: Registering input extension
Nov 17 22:40:36 minikat kernel: input: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/rc/rc1/input14
Nov 17 22:40:36 minikat kernel: rc1: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/rc/rc1
Nov 17 22:40:36 minikat kernel: em28174 #0: Input extension successfully initalized
Nov 17 22:40:36 minikat kernel: em28174 #1: Registering input extension
Nov 17 22:40:36 minikat kernel: input: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.2/rc/rc2/input15
Nov 17 22:40:36 minikat kernel: rc2: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.2/rc/rc2
Nov 17 22:40:36 minikat kernel: em28174 #1: Input extension successfully initalized
Nov 17 22:40:36 minikat kernel: em28xx: Registered (Em28xx Input Extension) extension

I think the above indicates the devices are separately recognized.

Last edited by replabrobin (2015-01-25 19:12:37)

crondog

Member

Registered: 2011-04-21

Posts: 130

Re: [SOLVED] Intel NUC using second dvb-t device causes usb lockup

Posting your dmesg with the usb enumeration lines would be helpful.

Also i have heard that there are issues when using identical tv tuners. Something like this might be of interest to you http://www.mythtv.org/wiki?title=Device … _option.29 if the issue is both of your tuners are being assigned the same device name

mcgrew

Member

Registered: 2010-10-26

Posts: 3

Re: [SOLVED] Intel NUC using second dvb-t device causes usb lockup

I'm having a similar problem with the WinTV HVR 950Q on my i7 laptop. Any time something (tvtime, ffplay, etc) tries to read from the device, USB dies with the same "Assuming host is dying" message in dmesg. Fortunately my laptop keyboard & touchpad aren't connected via usb, so I'm not forced to power cycle, but I'ld like to figure out the problem so I can use the device.

Currently I'm thinking there is a problem with the xhci driver module, but I'm still working on tracking it down. Let me know if you figure this out.

Update:

Just confirmed that at least in my case this is an issue with xhci. I compiled a kernel with no xhci support and booted to it (since blacklisting xhci_hcd doesn't seem to work), now the capture device seems to work properly. Unfortunately this means I can have USB3, or the capture device, but not both (for now).

There is a "quirks" parameter that can be passed to the xhci_hcd module. It seems to be a bitmask AFAICT, but I haven't been able to find any documentation as to what it does yet. Maybe there's something in there that can help here.

Last edited by mcgrew (2014-11-18 20:43:48)

replabrobin

Member

Registered: 2010-05-06

Posts: 234

Re: [SOLVED] Intel NUC using second dvb-t device causes usb lockup

So. am I right in thinking, that since I have no usb3 devices I should be able to blacklist xhci_hcd?
Edit: well I tried blacklisting xhci_hcd, but it didn't fix the issue.
Edit: when I tried this first I forgot the initramfs, when I fix that and xhci_hcd is definitely not loaded, then I find my usb keyboard is not seen. Had to boot off a rescue to fix

Last edited by replabrobin (2014-11-18 23:17:14)

dhead

Member

Registered: 2012-09-26

Posts: 190

Re: [SOLVED] Intel NUC using second dvb-t device causes usb lockup

Won't help, but it seem that this is related https://bugs.launchpad.net/ubuntu/+sour … ug/1313279

replabrobin

Member

Registered: 2010-05-06

Posts: 234

Re: [SOLVED] Intel NUC using second dvb-t device causes usb lockup

I have no permanent solution, but find that OpenElec has a fix

https://github.com/OpenELEC/OpenELEC.tv … 2e9be51e03

which reverts a change to xhci.c/h (47f467ac740ebf0475a5176ddb1741acba6aad4e)