11
« on: January 04, 2013, 13:40:57 »
Ich habe seit einiger Zeit ein seltsames Phänomen: Das externe Usb-Device (Technotrend 2400-usb) hängt sich aus von mir nicht nachvollziehbaren Gründen unregelmäßig aus. Manchmal nach zwei Tagen, manchmal nach wenigen Stunden.
Ich sehe keine Regel warum. Vielleicht hat jemand eine Idee?
Jan 4 13:15:50 (none) user.err vdr: [21458] epg data writer thread ended (pid=6417, tid=21458)
Jan 4 13:16:55 (none) user.err vdr: [21454] recording to '/mnt/data/tv/LiveBuffer/00005.ts'
Jan 4 13:18:44 (none) user.err vdr: [21454] Deleting old livebuffer file #1 (0)
Jan 4 12:19:10 (none) user.info kernel: usb 1-1: USB disconnect, device number 2
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (8/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (9/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 4 12:19:10 (none) user.err kernel: ttusb2: i2c transfer failed.
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (4/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
Jan 4 12:19:10 (none) user.err kernel: dvb-usb: bulk message failed: -19 (5/0)
Jan 4 12:19:10 (none) user.warn kernel: ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
Jan 4 13:19:17 (none) user.err vdr: [6417] EnigmaNG: cPluginSkinEnigma::LoadXpm(/etc/vdr/plugins/skinenigmang/logos/VOX.xpm) LOGO NOT FOUND/READABLE (No such file or directory)
Jan 4 13:19:17 (none) user.err vdr: [6417] EnigmaNG: cPluginSkinEnigma::LoadXpm(/etc/vdr/plugins/skinenigmang/logos/no_logo.xpm) LOGO NOT FOUND/READABLE (No such file or directory)
Jan 4 13:19:17 (none) user.err vdr: [6417] switching to channel 8
Jan 4 13:19:17 (none) user.err vdr: [21454] recording thread ended (pid=6417, tid=21454)
Jan 4 13:19:17 (none) user.err vdr: [6437] ERROR: frontend 0/0: No such device
Auffällig ist eigtl. nur der Zeitstempel, der zwischen Kernel und vdr um eine Stunde verschoben ist. Aber das kann ja kaum die Ursache des Aushängens sein.
Version ist 3.0.1, dvb-usb ist aktuell.
Hans