[vdr] Re: Big problem with scheduled recording

To: <vdr@linuxtv.org>
Subject: [vdr] Re: Big problem with scheduled recording
From: "Sebastian Herp" <newsletter@scytheman.net>
Date: Sun, 25 Nov 2001 19:10:22 +0100
Content-Transfer-Encoding: 8bit
Content-type: text/plain; charset=iso-8859-1
Delivered-To: mhonarc@limes.convergence.de
References: <00da01c175db$75595180$6401a8c0@omc.net>
Reply-to: vdr@linuxtv.org
Sender: vdr-bounce@linuxtv.org


PS.: The recording is perfect and complete

PPS.: the [...] are placeholders for several "error: failed to set PIDs for
channel xy" messages

PPPS.: I'm using VDR 0.98 (compiled with vfat=1 and remote=lirc) with the
dvb drivers from 21.9.2001

Greetings,
Sebastian

PPPPS.: The list seems not to accept mails bigger than 10 kb ... is that
normal?

----- Original Message -----
From: "Sebastian Herp" <newsletter@scytheman.net>
To: <vdr@linuxtv.org>
Sent: Sunday, November 25, 2001 7:02 PM
Subject: [vdr] Big problem with scheduled recording


>
> Hello list!
> I tried to send and resend and send and resend this email several times
...
> if you do not want to accept my mail please tell me so ... bad list you
...
> *knurr*
>
> I do not know what happened this evening with my vdr, but the syslog is
...
> ehm "full" :-(
>
> I scheduled "Star Trek - Der Aufstand" for recording and left the house.
> There were about 4-5 GB free diskspace .... so the diskspace can not be
the
> problem (1,6 GB left after the recording). The recording starts normally
but
> then ... wohoo ... the syslog is filled with endless "read imcomplete
> section"-messages. But that is not all ... there are very strange messages
> after the recording stopped ...
>
> Approximately one hour after VDR deleted the timer "Nov 24 22:40:00 milk
> vdr[460]: deleting timer 1", VDR randomly changes channels (only
> interpreting the syslog).
>
> Syslog-excerpt:
> ------------------------
> Nov 24 23:39:17 milk vdr[460]: ERROR: Transfer-Mode kann nicht gestartet
> werden!
> Nov 24 23:40:37 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 24 23:41:05 milk vdr[460]: ERROR: channel 54 not sync'ed on DVB card
1!
> Nov 24 23:41:05 milk vdr[460]: panic level: 0
> Nov 24 23:41:05 milk vdr[460]: retrying
> Nov 24 23:43:33 milk vdr[460]: ERROR: failed to set PIDs for channel 82
> Nov 24 23:43:33 milk vdr[460]: retrying
> [...]
> Nov 24 23:46:24 milk vdr[460]: ERROR: failed to set PIDs for channel 180
> Nov 24 23:46:24 milk vdr[460]: retrying
> Nov 24 23:48:56 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 24 23:48:56 milk vdr[460]: panic level: 0
> Nov 24 23:48:56 milk vdr[460]: retrying
> Nov 24 23:48:56 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 24 23:48:58 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 24 23:48:58 milk vdr[460]: panic level: 1
> Nov 24 23:48:58 milk vdr[460]: retrying
> Nov 24 23:48:58 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 24 23:49:01 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 24 23:49:01 milk vdr[460]: panic level: 2
> Nov 24 23:49:01 milk vdr[460]: retrying
> Nov 24 23:49:01 milk vdr[460]: max. latency time 8 seconds
> Nov 24 23:49:01 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 24 23:51:10 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 24 23:51:10 milk vdr[460]: panic level: 1
> Nov 24 23:51:10 milk vdr[460]: retrying
> Nov 24 23:51:10 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 24 23:51:13 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 24 23:51:13 milk vdr[460]: panic level: 2
> Nov 24 23:51:13 milk vdr[460]: retrying
> Nov 24 23:51:13 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 24 23:51:15 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 24 23:51:15 milk vdr[460]: panic level: 3
> Nov 24 23:51:15 milk vdr[460]: retrying
> Nov 24 23:51:15 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 24 23:59:05 milk vdr[460]: ERROR: Transfer-Mode kann nicht gestartet
> werden!
> Nov 25 00:00:14 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:00:14 milk vdr[460]: panic level: 2
> Nov 25 00:00:14 milk vdr[460]: retrying
> Nov 25 00:00:14 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:00:16 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:00:16 milk vdr[460]: panic level: 3
> Nov 25 00:00:16 milk vdr[460]: retrying
> Nov 25 00:00:16 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:00:19 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:00:19 milk vdr[460]: panic level: 4
> Nov 25 00:00:19 milk vdr[460]: retrying
> Nov 25 00:00:19 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:03:31 milk vdr[460]: ERROR: failed to set PIDs for channel 82
> Nov 25 00:03:31 milk vdr[460]: retrying
> [...]
> Nov 25 00:06:22 milk vdr[460]: ERROR: failed to set PIDs for channel 180
> Nov 25 00:06:22 milk vdr[460]: retrying
> Nov 25 00:08:54 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:08:54 milk vdr[460]: panic level: 3
> Nov 25 00:08:54 milk vdr[460]: retrying
> Nov 25 00:08:54 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:08:56 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:08:56 milk vdr[460]: panic level: 4
> Nov 25 00:08:56 milk vdr[460]: retrying
> Nov 25 00:08:56 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:08:58 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:08:58 milk vdr[460]: panic level: 5
> Nov 25 00:08:58 milk vdr[460]: retrying
> Nov 25 00:08:58 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:11:08 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:11:08 milk vdr[460]: panic level: 4
> Nov 25 00:11:08 milk vdr[460]: retrying
> Nov 25 00:11:08 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 25 00:11:10 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:11:10 milk vdr[460]: panic level: 5
> Nov 25 00:11:10 milk vdr[460]: retrying
> Nov 25 00:11:10 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 25 00:11:13 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:11:13 milk vdr[460]: panic level: 6
> Nov 25 00:11:13 milk vdr[460]: retrying
> Nov 25 00:11:13 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 25 00:19:02 milk vdr[460]: ERROR: Transfer-Mode kann nicht gestartet
> werden!
> Nov 25 00:20:12 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:20:12 milk vdr[460]: panic level: 5
> Nov 25 00:20:12 milk vdr[460]: retrying
> Nov 25 00:20:12 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:20:14 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:20:14 milk vdr[460]: panic level: 6
> Nov 25 00:20:14 milk vdr[460]: retrying
> Nov 25 00:20:14 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:20:17 milk vdr[460]: ERROR: channel 48 not sync'ed on DVB card
1!
> Nov 25 00:20:17 milk vdr[460]: panic level: 7
> Nov 25 00:20:17 milk vdr[460]: retrying
> Nov 25 00:20:17 milk kernel: mon_fail(0): freq=1036000000, sr=21997000
> Nov 25 00:23:28 milk vdr[460]: ERROR: failed to set PIDs for channel 82
> Nov 25 00:23:28 milk vdr[460]: retrying
> [...]
> Nov 25 00:26:20 milk vdr[460]: ERROR: failed to set PIDs for channel 180
> Nov 25 00:26:20 milk vdr[460]: retrying
> Nov 25 00:28:51 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:28:51 milk vdr[460]: panic level: 6
> Nov 25 00:28:51 milk vdr[460]: retrying
> Nov 25 00:28:51 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:28:54 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:28:54 milk vdr[460]: panic level: 7
> Nov 25 00:28:54 milk vdr[460]: retrying
> Nov 25 00:28:54 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:28:56 milk vdr[460]: ERROR: channel 229 not sync'ed on DVB card
1!
> Nov 25 00:28:56 milk vdr[460]: panic level: 8
> Nov 25 00:28:56 milk vdr[460]: retrying
> Nov 25 00:28:56 milk kernel: mon_fail(0): freq=1081000000, sr=21997000
> Nov 25 00:31:06 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:31:06 milk vdr[460]: panic level: 7
> Nov 25 00:31:06 milk vdr[460]: retrying
> Nov 25 00:31:06 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 25 00:31:08 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:31:08 milk vdr[460]: panic level: 8
> Nov 25 00:31:08 milk vdr[460]: retrying
> Nov 25 00:31:08 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> Nov 25 00:31:11 milk vdr[460]: ERROR: channel 264 not sync'ed on DVB card
1!
> Nov 25 00:31:11 milk vdr[460]: panic level: 9
> Nov 25 00:31:11 milk vdr[460]: retrying
> Nov 25 00:31:11 milk kernel: mon_fail(0): freq=1528000000, sr=27496000
> -------------------------------------
> strange, isn't it?
>
> at approximately 1 o'clock i came home ... the OSD of the VDR had strange
> colours, red and light green fontcolor ... almost unreadable ... VDR seems
> to
> work perfectly anyway...
>
> I deleted the appended complete syslog-excerpt ... this mailing-list
doesn't
> want me to post it (as it looks like *g*) ...
>
> Thanks,
> Sebastian Herp
>
>
>
>
>
>

Follow-Ups:
- [vdr] Re: Big problem with scheduled recording
  - From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>

References:
- [vdr] Big problem with scheduled recording
  - From: "Sebastian Herp" <newsletter@scytheman.net>

Prev by Date: [vdr] Big problem with scheduled recording
Next by Date: [vdr] MP3 extention 0.26 available
Prev by thread: [vdr] Big problem with scheduled recording
Next by thread: [vdr] Re: Big problem with scheduled recording
Index(es):
- Date
- Thread

Home | Main Index | Thread Index