Hallo,
nachdem ich wieder (nach einiger Zeit in unstable) per Snapshot zurück auf Testing gesetzt habe, wurden nochmals alle vorhandenen Updates eingespielt. Jetzt zeigt sich allerdings ein instabiles Verhalten, welches sich folgendermassen im Log darstellt:
Oct 22 07:27:03 (MLD) user.err epgd: State now 'busy (match)'
Oct 22 07:27:03 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40706 client connection accepted
Oct 22 07:27:03 (MLD) user.debug vdr: [2622] SVDRP < 192.168.10.28:40706 server created
Oct 22 07:27:03 (MLD) user.err epgd: Send 'PLUG epg2vdr STATE busy (match)' to 'epg2vdr' at '192.168.10.28:6419'
Oct 22 07:27:03 (MLD) user.err vdr: epg2vdr: Got epgd state 'busy (match)' (4)
Oct 22 07:27:03 (MLD) user.err vdr: epg2vdr: Change handler state to 'standby'
Oct 22 07:27:03 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40706 lost connection to client
Oct 22 07:27:03 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40706 connection closed
Oct 22 07:27:03 (MLD) user.debug vdr: [2622] SVDRP < 192.168.10.28:40706 server destroyed
Oct 22 07:27:15 (MLD) user.err vdr: video: 22:05:36.357 +39 330 0/\ms 36+3+4 v-buf
Oct 22 07:27:25 (MLD) user.err epgd: 1043 DVB pending, mergeepg done after 19.801 seconds
Oct 22 07:27:25 (MLD) user.err epgd: Checking timers against actual epg and searchtimer settings
Oct 22 07:27:25 (MLD) user.err epgd: Timers check done
Oct 22 07:27:25 (MLD) user.err epgd: AUTOTIMER: Updating searchtimers due to 'events changed' (force)
Oct 22 07:27:27 (MLD) user.err epgd: AUTOTIMER: Update done after 1.720 seconds, created (0) timers
Oct 22 07:27:27 (MLD) user.err epgd: State now 'standby'
Oct 22 07:27:27 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40710 client connection accepted
Oct 22 07:27:27 (MLD) user.debug vdr: [2622] SVDRP < 192.168.10.28:40710 server created
Oct 22 07:27:27 (MLD) user.err epgd: Send 'PLUG epg2vdr STATE standby' to 'epg2vdr' at '192.168.10.28:6419'
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Got epgd state 'standby' (1)
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Change handler state to 'active'
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Error: Channel with ID '00'' don't exist on this VDR
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Error: Channel with ID '30'' don't exist on this VDR
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Error: Channel with ID '45'' don't exist on this VDR
Oct 22 07:27:27 (MLD) user.info vdr: [2508] VNSI: Requesting clients to reload channel list
Oct 22 07:27:27 (MLD) user.info vdr: [2508] VNSI: Requesting clients to reload timers
Oct 22 07:27:27 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40710 lost connection to client
Oct 22 07:27:27 (MLD) user.info vdr: [2622] SVDRP < 192.168.10.28:40710 connection closed
Oct 22 07:27:27 (MLD) user.debug vdr: [2622] SVDRP < 192.168.10.28:40710 server destroyed
Oct 22 07:27:27 (MLD) user.err vdr: epg2vdr: Updated changes since '22.10.2017 07:26:25'; 161 channels, 746 events (0 deletions) in 172 ms
Oct 22 07:27:27 (MLD) user.info vdr: [2508] VNSI: Requesting clients to reload timers
Oct 22 07:27:27 (MLD) user.debug vdr: [4691] epg data writer thread started (pid=2307, tid=4691, prio=low)
Oct 22 07:27:28 (MLD) user.debug vdr: [4691] epg data writer thread ended (pid=2307, tid=4691)
Oct 22 07:27:32 (MLD) user.info vdr: [2508] VNSI: Requesting clients to reload channel list
Oct 22 07:27:52 (MLD) user.err kernel: [ 1107.680895] irq 123: nobody cared (try booting with the "irqpoll" option)
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680901] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 4.10.17.199.20 #1
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680903] Hardware name: FUJITSU D3401-B1/D3401-B1, BIOS V5.0.0.11 R1.17.0 for D3401-B1x 09/16/2016
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680905] Call Trace:
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680908] <IRQ>
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680926] ? dump_stack+0x5d/0x79
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680929] ? __report_bad_irq+0x36/0xb0
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680930] ? note_interrupt+0x19a/0x222
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680932] ? handle_irq_event_percpu+0x39/0x3f
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680933] ? handle_irq_event+0x22/0x43
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680935] ? default_inquire_remote_apic+0xf/0xf
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680936] ? handle_edge_irq+0xc7/0xe3
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680937] ? handle_irq+0x11/0x17
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680939] ? do_IRQ+0x3b/0xb5
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680940] ? common_interrupt+0x82/0x82
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680940] </IRQ>
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680942] ? cpuidle_enter_state+0xff/0x154
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680943] ? cpuidle_enter_state+0xb7/0x154
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680944] ? do_idle+0x10b/0x181
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680945] ? cpu_startup_entry+0x18/0x1a
Oct 22 07:27:52 (MLD) user.warn kernel: [ 1107.680946] ? start_cpu+0x14/0x14
Oct 22 07:27:52 (MLD) user.err kernel: [ 1107.680947] handlers:
Oct 22 07:27:52 (MLD) user.err kernel: [ 1107.680949] [<ffffffffa0194400>] irq_handler0 [ddbridge]
Oct 22 07:27:52 (MLD) user.emerg kernel: [ 1107.680950] Disabling IRQ #123
Oct 22 07:27:53 (MLD) user.err vdr: video/vdpau: missed frame (4/52168)
Oct 22 07:27:53 (MLD) user.err vdr: video: decoder buffer empty, duping frame (5/52867) 0 v-buf
Oct 22 07:27:53 (MLD) user.err vdr: video: 22:06:14.617+8888 0 0/\ms 0+1+4 v-buf
video>
Installiert ist dvb-mbe, da ddci2 an der enstprechenden Karte genutzt werden soll.
Unter unstable und einer früheren testing-Version traten diese Abstürze des DVB-Treibers nicht auf... Warum bin ich auf testing zurück? Weil in den letzten Versionen dort die DVB-Karte nicht erkannt wurde... Das ist aber ein anderes Thema.
Kann ich hier bei der Ursachenforschung unterstützen?
Gruss...
...Hagen
Users Online