USB Disconnect nach einstecken des MediaPro...

[marc]

Hallo Leute,

ich habe mal wieder das Problem das sich die TV-Sticks immer wieder Verabschieden.

Das Problem kann ich soweit lokalisieren: mit meinen 2x SkyTV Ultimate V (2015) habe ich keine Probleme, aber sobald ich den MediaTV Pro einstecke und in TVHeadend aktiviere gibt es immer wieder die Meldung das der Kernel die/den Stick kickt und kurze zeit später wieder (unter neuen Namen) einbindet (gleiche Kernel Meldung wie in meinem vorherigen Beitrag (...USB disconnect, device number...) http://support.sundtek.com/index.php/topic,2121.msg16836/topicseen.html#msg16836 ).

Wo kann das Problem liegen?
Verschiedene USB-Ports habe ich getestet, am System hat sich bis auf den Kernel (4.7.0-0.bpo.1-amd64) und das Mainboard (GIGABYTE N3150N-D3V) nichts geändert.

Danke für die Hilfe.

[Sundtek]

Was zeigt denn folgender Befehl an:

lsusb -t

[marc]

Was zeigt denn folgender Befehl an:

lsusb -t

Ohne den MediaTV Pro:

Code: [Auswählen]

lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
    |__ Port 3: Dev 2, If 0, Class=Printer, Driver=usblp, 12M
    |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 5: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 1, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 2, Class=Vendor Specific Class, Driver=usbfs, 480M
        |__ Port 2: Dev 5, If 3, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 4, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 5, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 6, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 1, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 2, Class=Vendor Specific Class, Driver=usbfs, 480M
            |__ Port 3: Dev 7, If 3, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 4, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 5, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 6, Class=Vendor Specific Class, Driver=, 480M
und mit:

Code: [Auswählen]

lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
    |__ Port 3: Dev 2, If 0, Class=Printer, Driver=usblp, 12M
    |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 5: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 1, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 2, Class=Vendor Specific Class, Driver=usbfs, 480M
        |__ Port 2: Dev 5, If 3, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 4, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 5, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 5, If 6, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 1, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 2, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 3, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 4, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 5, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 1: Dev 8, If 6, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 1, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 2, Class=Vendor Specific Class, Driver=usbfs, 480M
            |__ Port 3: Dev 7, If 3, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 4, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 5, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 7, If 6, Class=Vendor Specific Class, Driver=, 480M

[Sundtek]

Versuch mal im Bios auf USB 2.0 umzustellen, bzw ob es dort irgendwelche Einstellungen gibt.

[marc]

Versuch mal im Bios auf USB 2.0 umzustellen, bzw ob es dort irgendwelche Einstellungen gibt.

gibt es leider nicht. Es hängt aber auch keiner der Sticks an einem USB3-Port UND die beiden anderen Funktionieren ja auch wunderbar, es zickt lediglich der MediaTV Pro bzw. wenn ich den einstecke beginnen die Probleme. Auch eine Neustart bringt nix, das macht es eher noch schlimmer, da dann direkt nach dem Starten des mediasvr der Diconnect kommt und TVHeadend dann teilweise nur noch Neustartet (sundtec.conf -> ... tvheadend restart). Ansonsten habe ich keine Probleme, Aufnehmen und TV-Gucken zur gleichen zeit, Ondemand und aufnehmen... geht alles ohne Probleme.

EDIT: nicht nach dem Einstecken des Sticks, sondern nach Aktivieren in TVHeadend beginnen die Probleme

[Sundtek]

XHCI ist der USB 3.0 Controller.

Das Board wäre wohl besser mit Windows zu bedienen da Windows einen stabilen USB 3.0 Controller Treiber mitbringt. Selbst wenn die Tuner unter 480MBit gelistet werden es wird dennoch der XHCI Treiber verwendet welcher nicht wasserdicht ist unter Linux.

Was zeigt denn /opt/bin/mediaclient -e an wenn alle Tuner angeschlossen sind?

Auch was zeigt denn "dmesg" an wenn das Problem auftritt.

Versuche auch eventuell mal die Kabel untereinander zu wechseln.

[marc]

Code: [Auswählen]

**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate V (2015)]  DVB-S/S2, REMOTE-CONTROL
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 1-5.2
  [SERIAL]:
     ID: U160213185506
  [DVB-S/S2]:
     FESTATUS: ACTIVE
     LNBVOLTAGE: ENABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

device 1: [Sundtek SkyTV Ultimate V (2015)]  DVB-S/S2, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-5.4.3
  [SERIAL]:
     ID: U150619122826
  [DVB-S/S2]:
     FESTATUS: STANDBY
     LNBVOLTAGE: DISABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput1

device 2: [MediaTV Pro III USB (EU)]  DVB-C, DVB-T, DVB-T2, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-5.4.1
  [SERIAL]:
     ID: U150219010310
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput2
  [OSS]:
     OSS0: /dev/dsp0
dmesg und Kabeltausch werde ich morgen mal versuchen sonst steigt mir meine Freundin gleich aufs Dach. Habt ihr schon Neuigkeiten wann der USB3 Bug behoben wird bzw. gibt es Hoffnung mit dem Kernel 4.8? Im Netz finde ich leider keine info, nur Bug-Reports bestimmter Geräte.
Ach ja und Windows kommt mir nicht ins Haus dann lebe ich lieber noch ohne DVB-T ist eh eher ein Luxus-Problem ;-)

[Sundtek]

Schalte mal die Logfile ein /etc/sundtek.conf loglevel=min

Und lade dann die Logfile hoch /var/log/mediasrv.log

Wir arbeiten an USB 3.0 Tunern um die USB 3.0 Probleme bei diversen Boards in den Griff zu bekommen.

[marc]

So nun hier die Logs...

dmesg

[ 1047.047564] usb 1-5.2: USB disconnect, device number 5
[ 1047.260907] usb 1-5.2: new high-speed USB device number 9 using xhci_hcd
[ 1047.351642] usb 1-5.2: New USB device found, idVendor=2659, idProduct=1502
[ 1047.351667] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1047.351684] usb 1-5.2: Product: SkyTV Ultimate V 2016
[ 1047.351696] usb 1-5.2: Manufacturer: Sundtek
[ 1047.351709] usb 1-5.2: SerialNumber: U160213185506
[ 1048.393935] input: Sundtek Remote Control as /devices/virtual/input/input24
[ 1075.908494] TCP: request_sock_TCP: Possible SYN flooding on port 9982. Sending cookies.  Check SNMP counters.
[ 1097.480084] usb 1-5.2: USB disconnect, device number 9
[ 1097.690441] usb 1-5.2: new high-speed USB device number 10 using xhci_hcd
[ 1097.782969] usb 1-5.2: New USB device found, idVendor=2659, idProduct=1502
[ 1097.782993] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1097.783010] usb 1-5.2: Product: SkyTV Ultimate V 2016
[ 1097.783024] usb 1-5.2: Manufacturer: Sundtek
[ 1097.783037] usb 1-5.2: SerialNumber: U160213185506
[ 1099.484238] input: Sundtek Remote Control as /devices/virtual/input/input25

und /var/log/mediasvr.log ist im Anhang.
Was mir hier u.A. auffällt sind die letzten Zeilen, ist das normal das die Sticks in sleep gehen und 3 sec. später wieder Aufgewacht werden?

[Sundtek]

Versuche mal einen anderen Port um Tuner oder USB Port zu isolieren Es passiert auf dem Bus: "1-5.2"

Das Forum wäre voll damit wenn so etwas ständig passieren würde, zudem es bei uns auch nicht auftritt.
Der Tuner ist aus der 2016er Serie die haben soweit keine bekannten Probleme.

[marc]

Versuche mal einen anderen Port um Tuner oder USB Port zu isolieren Es passiert auf dem Bus: "1-5.2"

Das Forum wäre voll damit wenn so etwas ständig passieren würde, zudem es bei uns auch nicht auftritt.
Der Tuner ist aus der 2016er Serie die haben soweit keine bekannten Probleme.

passiert leider auch auf dem Port 1-5.4

Code: [Auswählen]

usb 1-5.4.3: USB disconnect, device number 17
jetzt mal ohne Witz! Warum hab nur ich ständig diese Probleme?!

Ich hab eine Nagelneue Debian 8 Installation mit dem 4.7er Kernel aus den Backports und TVHeadend aus deren stable Repo (4.0.9-13~g64fec81~jessie), sonst ist auf dem Server nix drauf.

[Sundtek]

Das einzige was wir hier machen können ist das Angebot die Tuner nach Berlin einzusenden und das wir das gleiche Setup bei uns versuchen nachzustellen.

XHCI ist halt ein "Risikofaktor"

[Immanuel]

Hallo zusammen, ich habe das gleiche Problem. Ebenfalls schon sehr lang.
Debian Jessie mit neuestem Backports Kernel (4.7) auf einem ASRock 3710 itx.
Ich kann den Stick z.T. überhaupt nicht benutzen, da er sich sporadisch aufhängt. Ausstecken, einstecken hilft temporär.

Code: [Auswählen]

[Fr Nov 11 20:40:39 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:40:41 2016] input: Sundtek Remote Control as /devices/virtual/input/input13
[Fr Nov 11 20:40:42 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 20:43:37 2016] usb 1-5.1: USB disconnect, device number 8
[Fr Nov 11 20:43:37 2016] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd
[Fr Nov 11 20:43:37 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Fr Nov 11 20:43:37 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Nov 11 20:43:37 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Fr Nov 11 20:43:37 2016] usb 1-5.1: Manufacturer: Sundtek
[Fr Nov 11 20:43:37 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:43:39 2016] input: Sundtek Remote Control as /devices/virtual/input/input14
[Fr Nov 11 20:43:40 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 20:51:28 2016] usb 1-5.1: USB disconnect, device number 9
[Fr Nov 11 20:51:29 2016] usb 1-5.1: new high-speed USB device number 10 using xhci_hcd
[Fr Nov 11 20:51:29 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Fr Nov 11 20:51:29 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Nov 11 20:51:29 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Fr Nov 11 20:51:29 2016] usb 1-5.1: Manufacturer: Sundtek
[Fr Nov 11 20:51:29 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:51:30 2016] input: Sundtek Remote Control as /devices/virtual/input/input15
[Fr Nov 11 20:51:31 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 20:51:50 2016] usb 1-5.1: USB disconnect, device number 10
[Fr Nov 11 20:51:50 2016] usb 1-5.1: new high-speed USB device number 11 using xhci_hcd
[Fr Nov 11 20:51:50 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Fr Nov 11 20:51:50 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Nov 11 20:51:50 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Fr Nov 11 20:51:50 2016] usb 1-5.1: Manufacturer: Sundtek
[Fr Nov 11 20:51:50 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:51:52 2016] input: Sundtek Remote Control as /devices/virtual/input/input16
[Fr Nov 11 20:51:53 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 20:52:11 2016] usb 1-5.1: USB disconnect, device number 11
[Fr Nov 11 20:52:11 2016] usb 1-5.1: new high-speed USB device number 12 using xhci_hcd
[Fr Nov 11 20:52:12 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Fr Nov 11 20:52:12 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Nov 11 20:52:12 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Fr Nov 11 20:52:12 2016] usb 1-5.1: Manufacturer: Sundtek
[Fr Nov 11 20:52:12 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:52:13 2016] input: Sundtek Remote Control as /devices/virtual/input/input17
[Fr Nov 11 20:52:14 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 20:53:54 2016] usb 1-5.1: USB disconnect, device number 12
[Fr Nov 11 20:53:55 2016] usb 1-5.1: new high-speed USB device number 13 using xhci_hcd
[Fr Nov 11 20:53:55 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Fr Nov 11 20:53:55 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Nov 11 20:53:55 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Fr Nov 11 20:53:55 2016] usb 1-5.1: Manufacturer: Sundtek
[Fr Nov 11 20:53:55 2016] usb 1-5.1: SerialNumber: U160801154933
[Fr Nov 11 20:53:56 2016] input: Sundtek Remote Control as /devices/virtual/input/input18
[Fr Nov 11 20:53:57 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Fr Nov 11 21:10:46 2016] usb 1-5.1: usbfs: process 3085 (mediasrv) did not claim interface 2 before use
[Sa Nov 12 00:33:33 2016] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[Sa Nov 12 01:25:48 2016] perf: interrupt took too long (3193 > 3131), lowering kernel.perf_event_max_sample_rate to 62500
[Sa Nov 12 01:56:49 2016] usb 1-5.1: USB disconnect, device number 13
[Sa Nov 12 01:56:50 2016] usb 1-5.1: new high-speed USB device number 14 using xhci_hcd
[Sa Nov 12 01:56:50 2016] usb 1-5.1: device descriptor read/64, error -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: device descriptor read/64, error -71                                                                  
[Sa Nov 12 01:56:50 2016] usb 1-5.1: new high-speed USB device number 15 using xhci_hcd
[Sa Nov 12 01:56:50 2016] usb 1-5.1: unable to read config index 0 descriptor/all
[Sa Nov 12 01:56:50 2016] usb 1-5.1: can't read configurations, error -71                                                                  
[Sa Nov 12 01:56:50 2016] usb 1-5.1: new high-speed USB device number 16 using xhci_hcd
[Sa Nov 12 01:56:50 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Sa Nov 12 01:56:50 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 8 len 4 ret -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 8 len 4 ret -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 8 len 4 ret -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 12 len 4 ret -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 5 len 4 ret -71
[Sa Nov 12 01:56:50 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 5 len 4 ret -71

...

[Sa Nov 12 01:56:52 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 01:56:52 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 01:56:52 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Sa Nov 12 01:56:52 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71

...

[Sa Nov 12 01:56:53 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Sa Nov 12 01:56:53 2016] usb 1-5.1: USB disconnect, device number 16
[Sa Nov 12 01:56:53 2016] usb 1-5.1: new high-speed USB device number 17 using xhci_hcd
[Sa Nov 12 01:56:53 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Sa Nov 12 01:56:53 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sa Nov 12 01:56:53 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Sa Nov 12 01:56:53 2016] usb 1-5.1: Manufacturer: Sundtek
[Sa Nov 12 01:56:53 2016] usb 1-5.1: SerialNumber: U160801154933
[Sa Nov 12 01:56:55 2016] input: Sundtek Remote Control as /devices/virtual/input/input20
[Sa Nov 12 01:56:56 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Sa Nov 12 02:02:28 2016] usb 1-5.1: USB disconnect, device number 17
[Sa Nov 12 02:02:28 2016] usb 1-5.1: new high-speed USB device number 18 using xhci_hcd
[Sa Nov 12 02:02:28 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Sa Nov 12 02:02:28 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sa Nov 12 02:02:28 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Sa Nov 12 02:02:28 2016] usb 1-5.1: Manufacturer: Sundtek
[Sa Nov 12 02:02:28 2016] usb 1-5.1: SerialNumber: U160801154933
[Sa Nov 12 02:02:29 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 4 ret -71
[Sa Nov 12 02:02:29 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 4 ret -71
[Sa Nov 12 02:02:30 2016] input: Sundtek Remote Control as /devices/virtual/input/input21
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 13 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 6 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 6 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 1 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 4 len 4 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 02:02:30 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 4 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
[Sa Nov 12 02:02:31 2016] usb 1-5.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Sa Nov 12 02:03:02 2016] usb 1-5.1: USB disconnect, device number 18
[Sa Nov 12 02:03:02 2016] usb 1-5.1: new high-speed USB device number 20 using xhci_hcd
[Sa Nov 12 02:03:02 2016] usb 1-5.1: New USB device found, idVendor=2659, idProduct=1502
[Sa Nov 12 02:03:02 2016] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sa Nov 12 02:03:02 2016] usb 1-5.1: Product: SkyTV Ultimate 6 2016/Q1
[Sa Nov 12 02:03:02 2016] usb 1-5.1: Manufacturer: Sundtek
[Sa Nov 12 02:03:02 2016] usb 1-5.1: SerialNumber: U160801154933
[Sa Nov 12 02:03:04 2016] input: Sundtek Remote Control as /devices/virtual/input/input22
[Sa Nov 12 02:03:05 2016] usb 1-5.1: usbfs: process 1119 (mediasrv) did not claim interface 0 before use
[Sa Nov 12 02:04:02 2016] usb 1-5.1: usbfs: process 6078 (mediasrv) did not claim interface 2 before use
[Sa Nov 12 04:05:42 2016] perf: interrupt took too long (4052 > 3991), lowering kernel.perf_event_max_sample_rate to 49250


[Sundtek]

XHCI USB 3.0 ...  die sind einfach schlecht unterstützt von Linux.

versucht mal die Fernbedienung abzuschalten
/etc/sundtek.conf
ir_disabled=1

Anzahl USB 2.0 intern für Frontanschluss   2
Anzahl USB 2.0 Rückplatine   2

versuche einen nativen USB 2.0 Anschluss zu verwenden

lsusb -t sollte den Tuner unter EHCI anzeigen nicht unter XHCI

Es gibt wohl ein paar XHCI Controller die keine Probleme haben mit USB 2.0 Tunern, aber es sind halt wohl nicht alle.

Auch wichtig Netzteil verwenden um das als Fehlerquelle auszuschließen.

/opt/bin/mediaclient -e soll ACADAPTER anzeigen.

Bei Asus Systemen auch die BIOS Version auf Updates überprüfen.

Einfach mal mit google gesucht:

I have one of these and also the N3150 version - they are great for Kodi use BUT they have crippled USB 3.0 ports!

Four of the ports are conrtolled by an ASMedia ASM1074 usb hub and it is broken - if a UASP usb device is connected it keeps resetting every ~30 seconds or so. The remaining two ports are also broken and Intel had to issue a special usb driver to cope with a design issue.

If you want to deal with constant USB 3.0 disconnects then OK you have been warned. The new J3710 and J3160 boards still use the same crippled ASMedia ASM1074 chip - don't know if Intel have solved the other USB3.0 issue on these new revisions.

All very disappointing for an otherwise good silent HTPC solution.

[marc]

"Sehr gut" ich bin nicht der einzige.

IR habe ich schon bei der Treiber Installation deaktiviert und auch in der sundtec.conf von vornherein deaktiviert.
Der Media Pro hat kein Netzteil und die beiden Sky hängen an ihren Netzteilen.

Zitat
I have one of these and also the N3150 version - they are great for Kodi use BUT they have crippled USB 3.0 ports!

Four of the ports are conrtolled by an ASMedia ASM1074 usb hub and it is broken - if a UASP usb device is connected it keeps resetting every ~30 seconds or so. The remaining two ports are also broken and Intel had to issue a special usb driver to cope with a design issue.

If you want to deal with constant USB 3.0 disconnects then OK you have been warned. The new J3710 and J3160 boards still use the same crippled ASMedia ASM1074 chip - don't know if Intel have solved the other USB3.0 issue on these new revisions.

All very disappointing for an otherwise good silent HTPC solution.

Das kann ich so nicht bestätigen. Ich habe am hinteren USB3-Port eine externe USB3-Platte hängen und die funktioniert tadellos (keine Aussetzer, Disconnects, o.Ä.) und damit Streame ich BluRay's (~20GB/h).

Ich werde bei Gelegenheit mal noch andere Geräte mit der MediaPro testen und dann mit logs berichten.

EDIT: Hier noch ein paar Infos zu meinem Board:
dmidecode -t bios

Code: [Auswählen]

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: F4
Release Date: 04/11/2016
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.11

Handle 0x0033, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1Bios ist aktuell

dmidecode | grep -i product

Code: [Auswählen]

Product Name: Default string
Product Name: N3150ND3V
Grüße