Moin,
mein VDR schmiert seit einiger Zeit mittendrin einfach unmotiviuert ab. MAn sieht das YaVDR-Logo, dann kommt der vdr wieder hoch.
Hier mal ein Ausschnitt aus den Logs zu diesem Zeitpunkt:
Code
Dec 9 23:15:08 vdr vdr: video: slow down video, duping frame
Dec 9 23:15:08 vdr vdr: video: decoder buffer empty, duping frame (19651/36) 0 v-buf
Dec 9 23:15:08 vdr vdr: video: --:--:--.--- +0 0 0/\ms 0+5 v-buf
Dec 9 23:15:08 vdr vdr: codec: buggy libav, use ffmpeg
Dec 9 23:15:08 vdr vdr: video: decoder buffer empty, duping frame (19678/36) 0 v-buf
Dec 9 23:15:08 vdr vdr: video: slow down video, duping frame
Dec 9 23:15:08 vdr vdr: video: 12:28:00.133 +600 433 0/\ms 0+1 v-buf
Dec 9 23:15:09 vdr vdr: video: slow down video, duping frame
Dec 9 23:15:09 vdr vdr: video/vdpau: missed frame (46/8)
Dec 9 23:15:09 vdr vdr: video: slow down video, duping frame
Dec 9 23:15:09 vdr vdr: video: 12:28:00.153 +556 490 0/\ms 2+8 v-buf
Dec 9 23:15:10 vdr vdr: video/vdpau: synced after 90 frames
Dec 9 23:15:12 vdr vdr: Message received org.freedesktop.UDisks#012 Member DeviceChanged
Dec 9 23:15:12 vdr vdr: DeviceChange Signal for /org/freedesktop/UDisks/devices/sda
Dec 9 23:15:12 vdr vdr: Path : /org/freedesktop/UDisks/devices/sda
Dec 9 23:15:12 vdr vdr: NativePath : /sys/devices/pci0000:00/0000:00:09.0/ata3/host2/target2:0:0/2:0:0:0/block/sda
Dec 9 23:15:12 vdr vdr: Type :
Dec 9 23:15:12 vdr vdr: Device File: /dev/sda
Dec 9 23:15:12 vdr vdr: Media Available
Dec 9 23:15:12 vdr vdr: ******** Detect ********
Dec 9 23:15:12 vdr vdr: AutoMount DeviceKit Error dbusdevkit.cc, 512, dbus_connection_send_with_reply failedDid not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 9 23:15:13 vdr vdr: AutoMount DeviceKit Error dbusdevkit.cc, 328, dbus_connection_send_with_reply failedConnection is closed
Dec 9 23:15:14 vdr vdr: AutoMount DeviceKit Error dbusdevkit.cc, 328, dbus_connection_send_with_reply failedConnection is closed
Dec 9 23:15:15 vdr vdr: Automount failed
Dec 9 23:15:15 vdr vdr: Add Device /dev/sda to device set
Dec 9 23:15:15 vdr kernel: [53955.753537] init: vdr main process (10521) terminated with status 1
Dec 9 23:15:15 vdr kernel: [53955.760792] init: vdr-frontend main process (10651) killed by TERM signal
Dec 9 23:15:16 vdr vdr-crash: vdr exit with exit status 1 . Restarting
Dec 9 23:15:16 vdr kernel: [53955.825374] init: vdr-exit-other main process (11054) terminated with status 1
Dec 9 23:15:16 vdr vdr: [11058] VDR version 2.0.6 started
Dec 9 23:15:16 vdr vdr: [11058] switched to user 'vdr'Und dmesg sagt:
Code
[51979.869441] dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)
[52157.529262] init: vdr main process (10005) terminated with status 1
[52157.536398] init: vdr-frontend main process (10135) killed by TERM signal
[52157.595471] init: vdr-exit-other main process (10517) terminated with status 1
[53254.521713] DVB (dvb_dmxdev_filter_start): could not set feed
[53254.521728] dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)
[53955.753537] init: vdr main process (10521) terminated with status 1
[53955.760792] init: vdr-frontend main process (10651) killed by TERM signal
[53955.825374] init: vdr-exit-other main process (11054) terminated with status 1Sieht hier jemand spontan warum der mir abschmiert?
Zuerst dachte ich das der SATA-Controller oder die SSD einen weg hat (wegen der Automounter-Meldungen im Log), aber ich müsste es im dmesg sehen wenn die Platte weg wäre und danach wieder auftauchen würde.
Wenn ihr mehr infos braucht: Nur zu....