[1] MLD-5.x / Systems / Raspberry PI / System friert immer ein
 

Offline GeforceGamer

  • Newbie
  • *
  • Posts: 15
    • View Profile
System friert immer ein
« on: August 16, 2015, 16:23:12 »
Hallo,

und zwar haben ich das pi 2 netimage für die Installation benutzt. Ich verwende VDR als Oberfläche mit Streamdev-Client zur übertragenung. Allerdings friert mein System immer nach 10-15 min ein und es funktioniert erst wieder wenn ich den VDR neu startet.


Log vom pi 2 mit MLD 5
Code: [Select]
Aug 16 16:05:22 (none) user.warn kernel: [  137.288732] ------------[ cut here ]------------
Aug 16 16:05:22 (none) user.warn kernel: [  137.288826] WARNING: CPU: 0 PID: 0 at net/core/skbuff.c:4104 skb_try_coalesce+0x364/0x3c0()
Aug 16 16:05:22 (none) user.warn kernel: [  137.288901] Modules linked in: lirc_rpi(O) lirc_dev(O) snd_soc_bcm2708_i2s regmap_mmio snd_soc_core snd_compress snd_pcm_dmaengine fuse uinput snd_bcm2835 snd_pcm snd_timer snd
Aug 16 16:05:22 (none) user.warn kernel: [  137.289004] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O   3.19.3.177 #1
Aug 16 16:05:22 (none) user.warn kernel: [  137.289015] Hardware name: BCM2709
Aug 16 16:05:22 (none) user.warn kernel: [  137.289063] [<80017358>] (unwind_backtrace) from [<80012f6c>] (show_stack+0x20/0x24)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289093] [<80012f6c>] (show_stack) from [<806e11f4>] (dump_stack+0x9c/0xdc)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289123] [<806e11f4>] (dump_stack) from [<80026058>] (warn_slowpath_common+0x98/0xc8)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289148] [<80026058>] (warn_slowpath_common) from [<80026144>] (warn_slowpath_null+0x2c/0x34)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289171] [<80026144>] (warn_slowpath_null) from [<805fb154>] (skb_try_coalesce+0x364/0x3c0)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289202] [<805fb154>] (skb_try_coalesce) from [<806563d8>] (tcp_try_coalesce.part.40+0x38/0xbc)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289228] [<806563d8>] (tcp_try_coalesce.part.40) from [<80657c1c>] (tcp_data_queue+0x7a4/0xc94)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289254] [<80657c1c>] (tcp_data_queue) from [<806599e8>] (tcp_rcv_established+0x148/0x628)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289281] [<806599e8>] (tcp_rcv_established) from [<80661e88>] (tcp_v4_do_rcv+0x154/0x390)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289309] [<80661e88>] (tcp_v4_do_rcv) from [<8066495c>] (tcp_v4_rcv+0x8a8/0x8b0)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289340] [<8066495c>] (tcp_v4_rcv) from [<8063fe18>] (ip_local_deliver_finish+0xf0/0x2d8)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289368] [<8063fe18>] (ip_local_deliver_finish) from [<80640564>] (ip_local_deliver+0x48/0xa8)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289394] [<80640564>] (ip_local_deliver) from [<80640164>] (ip_rcv_finish+0x164/0x3ec)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289419] [<80640164>] (ip_rcv_finish) from [<80640934>] (ip_rcv+0x370/0x498)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289447] [<80640934>] (ip_rcv) from [<80605e3c>] (__netif_receive_skb_core+0x68c/0x8a0)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289476] [<80605e3c>] (__netif_receive_skb_core) from [<806087c8>] (__netif_receive_skb+0x20/0x7c)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289503] [<806087c8>] (__netif_receive_skb) from [<8060a238>] (process_backlog+0xb0/0x150)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289527] [<8060a238>] (process_backlog) from [<8060a014>] (net_rx_action+0x284/0x3f8)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289550] [<8060a014>] (net_rx_action) from [<8002a190>] (__do_softirq+0x19c/0x3f0)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289575] [<8002a190>] (__do_softirq) from [<8002a7ec>] (irq_exit+0xdc/0x140)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289603] [<8002a7ec>] (irq_exit) from [<8006d7fc>] (__handle_domain_irq+0x98/0xec)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289631] [<8006d7fc>] (__handle_domain_irq) from [<8000855c>] (asm_do_IRQ+0x2c/0x30)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289681] [<8000855c>] (asm_do_IRQ) from [<806e68b4>] (__irq_svc+0x34/0x14c)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289697] Exception stack(0x809fff08 to 0x809fff50)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289717] ff00:                   ffffffed 00000000 ffffffed 00000000 809fe000 80a22cb4
Aug 16 16:05:22 (none) user.warn kernel: [  137.289738] ff20: 80a22d18 80a69f9c 00000000 00000000 00000000 809fff5c 80a23c18 809fff50
Aug 16 16:05:22 (none) user.warn kernel: [  137.289754] ff40: 8000fb28 8000fb2c 60000013 ffffffff
Aug 16 16:05:22 (none) user.warn kernel: [  137.289781] [<806e68b4>] (__irq_svc) from [<8000fb2c>] (arch_cpu_idle+0x34/0x4c)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289811] [<8000fb2c>] (arch_cpu_idle) from [<8005f9ec>] (cpu_startup_entry+0x2a0/0x39c)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289839] [<8005f9ec>] (cpu_startup_entry) from [<806ddc08>] (rest_init+0x94/0x98)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289870] [<806ddc08>] (rest_init) from [<8098bd34>] (start_kernel+0x3e8/0x3f4)
Aug 16 16:05:22 (none) user.warn kernel: [  137.289887] ---[ end trace 014f69400d4febec ]---
Aug 16 16:12:48 (none) user.err vdr: [1628] cStreamdevFilters::Action(): stream disconnected ?
Aug 16 16:13:01 (none) user.err vdr: [1552] ERROR: streamdev-client: Failed reading reply to 'ADDF 800 2 255' from 192.168.1.25:2004: Connection timed out
Aug 16 16:13:01 (none) user.err vdr: [1628] ERROR: streamdev-client: Failed sending command 'ABRT 2' to 0.0.0.0:0: Connection timed out
Aug 16 16:13:01 (none) user.err vdr: [1627] ERROR (device.c,1805): Bad file descriptor
Aug 16 16:13:30 (none) user.err vdr: [1494] PANIC: watchdog timer expired - exiting!

Log von yaVDR Server
Code: [Select]
Aug 16 15:36:13 yavdr-server vdr: [2488] frontend 1/0 timed out while tuning to channel 588 (RTL4), tp 112343
Aug 16 15:39:33 yavdr-server vdr: [2489] changing pids of channel 126 (ORF1) from 160+160=2:161=deu@3;163=deu@106:0:165 to 160+160=2:161=deu@3,162=deu@3;163=deu@106:0:165
Aug 16 15:43:30 yavdr-server vdr: [27717] epg data writer thread started (pid=2423, tid=27717, prio=low)
Aug 16 15:43:32 yavdr-server vdr: [27717] epg data writer thread ended (pid=2423, tid=27717)
Aug 16 15:43:46 yavdr-server vdr: [2489] changing ca descriptors of channel 811 (TAQUILLA 3)
Aug 16 15:43:46 yavdr-server vdr: [2489] changing caids of channel 813 (TAQUILLA XX) from 0 to 100,1810
Aug 16 15:43:46 yavdr-server vdr: [2489] changing ca descriptors of channel 813 (TAQUILLA XX)
Aug 16 15:45:00 yavdr-server vdr: [2515] EPGSearch: timer conflict check started
Aug 16 15:45:00 yavdr-server vdr: [2515] EPGSearch: timer conflict check finished
Aug 16 15:47:16 yavdr-server vdr: [2489] ERROR: can't set filter (pid=65535, tid=02, mask=FF): Das Argument ist ungültig
Aug 16 15:47:16 yavdr-server kernel: [228689.870499] DVB (dvb_dmxdev_filter_start): could not set feed
Aug 16 15:47:16 yavdr-server kernel: [228689.870506] dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)
Aug 16 15:53:18 yavdr-server rpc.mountd[1455]: refused mount request from 192.168.1.81 for /mnt/data (/): not exported
Aug 16 15:53:26  rpc.mountd[1455]: last message repeated 3 times
Aug 16 15:53:26 yavdr-server vdr: [2423] connect from 192.168.1.81, port 48538 - accepted
Aug 16 15:53:26 yavdr-server vdr: [2423] closing SVDRP connection
Aug 16 15:53:27 yavdr-server vdr: [2423] connect from 192.168.1.81, port 48539 - accepted
Aug 16 15:53:27 yavdr-server vdr: [2423] closing SVDRP connection
Aug 16 15:53:31 yavdr-server vdr: [27777] epg data writer thread started (pid=2423, tid=27777, prio=low)
Aug 16 15:53:33 yavdr-server vdr: [27777] epg data writer thread ended (pid=2423, tid=27777)
Aug 16 15:53:48 yavdr-server vdr: [2495] Streamdev: Accepted new client (VTP) 192.168.1.81:36581
Aug 16 15:53:48 yavdr-server vdr: [2495] too many PIDs in cReceiver (Pid = 1864397413)
Aug 16 15:53:48 yavdr-server vdr: [2495] Streamdev: Setting data connection to 192.168.1.81:36541
Aug 16 15:53:48 yavdr-server vdr: [27782] streamdev-filterstreaming thread started (pid=2423, tid=27782, prio=high)
Aug 16 15:53:48 yavdr-server vdr: [27781] streamdev-writer thread started (pid=2423, tid=27781, prio=high)
Aug 16 15:53:48 yavdr-server vdr: [2495] Streamdev: Setting data connection to 192.168.1.81:54374
Aug 16 15:53:48 yavdr-server vdr: [27784] streamdev-livestreaming thread started (pid=2423, tid=27784, prio=high)
Aug 16 15:53:48 yavdr-server vdr: [27783] streamdev-writer thread started (pid=2423, tid=27783, prio=high)
Aug 16 15:53:48 yavdr-server vdr: [27785] device 2 receiver thread started (pid=2423, tid=27785, prio=high)
Aug 16 15:53:49 yavdr-server vdr: [27786] TS buffer on device 2 thread started (pid=2423, tid=27786, prio=high)
Aug 16 15:54:54 yavdr-server vdr: [27785] buffer usage: 70% (tid=27784)
Aug 16 15:54:54 yavdr-server vdr: [27785] buffer usage: 80% (tid=27784)
Aug 16 15:54:54 yavdr-server vdr: [27785] buffer usage: 90% (tid=27784)
Aug 16 15:54:55 yavdr-server vdr: [27785] ERROR: 1 ring buffer overflow (188 bytes dropped)
Aug 16 15:55:00 yavdr-server vdr: [27783] ERROR: streamdev-server: couldn't send data: Die Wartezeit für die Verbindung ist abgelaufen
Aug 16 15:55:00 yavdr-server vdr: [27783] streamdev-writer thread ended (pid=2423, tid=27783)
Aug 16 15:55:00 yavdr-server vdr: [27781] ERROR: streamdev-server: couldn't send data: Die Wartezeit für die Verbindung ist abgelaufen
Aug 16 15:55:00 yavdr-server vdr: [27781] streamdev-writer thread ended (pid=2423, tid=27781)
Aug 16 15:55:00 yavdr-server vdr: [2495] streamdev-server: closing VTP connection to 192.168.1.81:36581
Aug 16 15:55:00 yavdr-server vdr: [27784] streamdev-livestreaming thread ended (pid=2423, tid=27784)
Aug 16 15:55:00 yavdr-server vdr: [27786] TS buffer on device 2 thread ended (pid=2423, tid=27786)
Aug 16 15:55:00 yavdr-server vdr: [27785] buffer stats: 105092 (2%) used
Aug 16 15:55:00 yavdr-server vdr: [27785] device 2 receiver thread ended (pid=2423, tid=27785)
Aug 16 15:55:01 yavdr-server vdr: [27782] streamdev-filterstreaming thread ended (pid=2423, tid=27782)
Aug 16 15:55:01 yavdr-server vdr: [2495] buffer stats: 3759813 (99%) used
Aug 16 15:55:04 yavdr-server rpc.mountd[1455]: refused mount request from 192.168.1.81 for /mnt/data (/): not exported
Aug 16 15:55:14  rpc.mountd[1455]: last message repeated 3 times
Aug 16 15:55:14 yavdr-server vdr: [2423] connect from 192.168.1.81, port 58320 - accepted
Aug 16 15:55:14 yavdr-server vdr: [2423] closing SVDRP connection
Aug 16 15:55:15 yavdr-server vdr: [2423] connect from 192.168.1.81, port 58321 - accepted
Aug 16 15:55:15 yavdr-server vdr: [2423] closing SVDRP connection
Aug 16 15:55:19 yavdr-server vdr: [2489] changing pids of channel 207 (Test-R) from 401+401=2:402=deu@3:0:0 to 501+501=2:502=deu@3:0:0
Aug 16 15:55:34 yavdr-server vdr: [2495] Streamdev: Accepted new client (VTP) 192.168.1.81:40475
Aug 16 15:55:34 yavdr-server vdr: [2495] too many PIDs in cReceiver (Pid = 1864397413)
Aug 16 15:55:34 yavdr-server vdr: [2495] Streamdev: Setting data connection to 192.168.1.81:38546
Aug 16 15:55:34 yavdr-server vdr: [27795] streamdev-filterstreaming thread started (pid=2423, tid=27795, prio=high)
Aug 16 15:55:34 yavdr-server vdr: [27794] streamdev-writer thread started (pid=2423, tid=27794, prio=high)
Aug 16 15:55:34 yavdr-server vdr: [2495] Streamdev: Setting data connection to 192.168.1.81:52228
Aug 16 15:55:34 yavdr-server vdr: [27797] streamdev-livestreaming thread started (pid=2423, tid=27797, prio=high)
Aug 16 15:55:34 yavdr-server vdr: [27796] streamdev-writer thread started (pid=2423, tid=27796, prio=high)
Aug 16 15:55:35 yavdr-server vdr: [27798] device 2 receiver thread started (pid=2423, tid=27798, prio=high)
Aug 16 15:55:35 yavdr-server vdr: [27799] TS buffer on device 2 thread started (pid=2423, tid=27799, prio=high)
Aug 16 16:03:32 yavdr-server vdr: [27805] epg data writer thread started (pid=2423, tid=27805, prio=low)
Aug 16 16:03:33 yavdr-server vdr: [27805] epg data writer thread ended (pid=2423, tid=27805)
Aug 16 16:04:25 yavdr-server vdr: [27798] buffer usage: 70% (tid=27797)
Aug 16 16:04:25 yavdr-server vdr: [27798] buffer usage: 80% (tid=27797)
Aug 16 16:04:26 yavdr-server vdr: [27798] buffer usage: 90% (tid=27797)
Aug 16 16:04:26 yavdr-server vdr: [27798] ERROR: 1 ring buffer overflow (188 bytes dropped)
Aug 16 16:04:31 yavdr-server vdr: [27796] ERROR: streamdev-server: couldn't send data: Die Wartezeit für die Verbindung ist abgelaufen
Aug 16 16:04:31 yavdr-server vdr: [27796] streamdev-writer thread ended (pid=2423, tid=27796)
Aug 16 16:04:32 yavdr-server vdr: [27798] ERROR: 29569 ring buffer overflows (5558972 bytes dropped)
Aug 16 16:04:32 yavdr-server vdr: [2495] streamdev-server: closing VTP connection to 192.168.1.81:40475
Aug 16 16:04:32 yavdr-server vdr: [27797] streamdev-livestreaming thread ended (pid=2423, tid=27797)
Aug 16 16:04:32 yavdr-server vdr: [27799] TS buffer on device 2 thread ended (pid=2423, tid=27799)
Aug 16 16:04:32 yavdr-server vdr: [27798] buffer stats: 122200 (2%) used
Aug 16 16:04:32 yavdr-server vdr: [27798] device 2 receiver thread ended (pid=2423, tid=27798)
Aug 16 16:04:32 yavdr-server vdr: [27795] streamdev-filterstreaming thread ended (pid=2423, tid=27795)
Aug 16 16:04:32 yavdr-server vdr: [27794] streamdev-writer thread ended (pid=2423, tid=27794)
Aug 16 16:04:32 yavdr-server vdr: [2495] buffer stats: 3759813 (99%) used
Aug 16 16:04:47 yavdr-server vdr: [2495] Streamdev: Accepted new client (VTP) 192.168.1.81:32963
Aug 16 16:04:48 yavdr-server vdr: [2489] changing pids of channel 207 (Test-R) from 501+501=2:502=deu@3:0:0 to 401+401=2:402=deu@3:0:0
Aug 16 16:06:10 yavdr-server vdr: [2489] ERROR: can't set filter (pid=65535, tid=02, mask=FF): Das Argument ist ungültig
Aug 16 16:06:10 yavdr-server kernel: [229823.887313] DVB (dvb_dmxdev_filter_start): could not set feed
Aug 16 16:06:10 yavdr-server kernel: [229823.887339] dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)
Aug 16 16:07:43 yavdr-server vdr: [2488] frontend 1/0 timed out while tuning to channel 1196 (AB Channel OBSOLETE), tp 111023

Hat jemand eine Idee wo das Problem liegt? Ich habe noch einen easyVDR Client der Problemlos funktioniert.

[1] MLD-5.x / Systems / Raspberry PI / System friert immer ein
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.