LinHES Forums :: View topic - Apparent fix for some zero length recordings on 5D1

stream: start_time: 0.276 duration: 28320.966 bitrate=1093 kb/s
2006-09-27 02:00:01.151 AFD: Opened codec 0x86b9170, id(MPEG2VIDEO) type(Video)
2006-09-27 02:00:01.204 AFD: Opened codec 0x86bec90, id(MP2) type(Audio)
2006-09-27 02:00:03.057 TVRec(2): Changing from None to RecordingOnly
2006-09-27 02:00:03.093 DVB#1 Using DVB card 1, with frontend 'Conexant CX22702 DVB-T'.
2006-09-27 02:00:03.254 Started recording: Future Fighting Machines: channel 1567 on cardid 2, sourceid 1
2006-09-27 02:00:03.269 scheduler: Last message repeated 1 times: Finished recording: [adult swim]: channel 1601
2006-09-27 02:00:03.281 scheduler: Started recording: Future Fighting Machines: channel 1567 on cardid 2, sourceid 1
2006-09-27 02:00:04.147 DVB#1 DVB SI Table Parser Started
2006-09-27 02:00:04.284 Reschedule requested for id 0.
2006-09-27 02:00:04.592 DVBRec(1) Error: Failed to open DVB device
eno: Cannot allocate memory (12)
2006-09-27 02:00:04.761 Scheduled 88 items in 0.5 = 0.00 match + 0.48 place
2006-09-27 02:00:04.771 scheduler: Scheduled items: Scheduled 88 items in 0.5 = 0.00 match + 0.48 place
2006-09-27 02:00:11.834 DVB#1 ERROR - Failed to set demux buffer size (pid 18)
(12) Cannot allocate memory
[mpeg2video @ 0xb70b2620]ac-tex damaged at 27 18
[mpeg2video @ 0xb70b2620]Warning MVs not available

{snippage}

2006-09-27 02:25:00.860 TVRec(2): Changing from RecordingOnly to None
2006-09-27 02:25:01.393 Finished recording Future Fighting Machines: channel 1567
2006-09-27 02:25:01.394 Reschedule requested for id 0.
2006-09-27 02:25:01.398 scheduler: Finished recording: Future Fighting Machines: channel 1567
2006-09-27 02:25:01.860 Finished recording Future Fighting Machines: channel 1567
2006-09-27 02:25:01.934 Scheduled 86 items in 0.5 = 0.01 match + 0.53 place
2006-09-27 02:25:01.944 scheduler: Last message repeated 1 times: Finished recording: Future Fighting Machines: channel 1567
2006-09-27 02:25:01.935 Preview Error: Previewer file '/myth/tv/1567_20060927020000.mpg' is not valid.
[mpeg2video @ 0xb6fff620]ac-tex damaged at 9 3
[mpeg2video @ 0xb6fff620]Warning MVs not available

allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.

Author:	bruce_s01 [ Thu Sep 28, 2006 8:56 am ]
Post subject:	Apparent fix for some zero length recordings on 5D1
When carrying out simultaneous recordings using 2 Nova-T DVB cards, one of the recordings sometimes ended up zero length From mythbackend.log Code: stream: start_time: 0.276 duration: 28320.966 bitrate=1093 kb/s 2006-09-27 02:00:01.151 AFD: Opened codec 0x86b9170, id(MPEG2VIDEO) type(Video) 2006-09-27 02:00:01.204 AFD: Opened codec 0x86bec90, id(MP2) type(Audio) 2006-09-27 02:00:03.057 TVRec(2): Changing from None to RecordingOnly 2006-09-27 02:00:03.093 DVB#1 Using DVB card 1, with frontend 'Conexant CX22702 DVB-T'. 2006-09-27 02:00:03.254 Started recording: Future Fighting Machines: channel 1567 on cardid 2, sourceid 1 2006-09-27 02:00:03.269 scheduler: Last message repeated 1 times: Finished recording: [adult swim]: channel 1601 2006-09-27 02:00:03.281 scheduler: Started recording: Future Fighting Machines: channel 1567 on cardid 2, sourceid 1 2006-09-27 02:00:04.147 DVB#1 DVB SI Table Parser Started 2006-09-27 02:00:04.284 Reschedule requested for id 0. 2006-09-27 02:00:04.592 DVBRec(1) Error: Failed to open DVB device eno: Cannot allocate memory (12) 2006-09-27 02:00:04.761 Scheduled 88 items in 0.5 = 0.00 match + 0.48 place 2006-09-27 02:00:04.771 scheduler: Scheduled items: Scheduled 88 items in 0.5 = 0.00 match + 0.48 place 2006-09-27 02:00:11.834 DVB#1 ERROR - Failed to set demux buffer size (pid 18) (12) Cannot allocate memory [mpeg2video @ 0xb70b2620]ac-tex damaged at 27 18 [mpeg2video @ 0xb70b2620]Warning MVs not available {snippage} 2006-09-27 02:25:00.860 TVRec(2): Changing from RecordingOnly to None 2006-09-27 02:25:01.393 Finished recording Future Fighting Machines: channel 1567 2006-09-27 02:25:01.394 Reschedule requested for id 0. 2006-09-27 02:25:01.398 scheduler: Finished recording: Future Fighting Machines: channel 1567 2006-09-27 02:25:01.860 Finished recording Future Fighting Machines: channel 1567 2006-09-27 02:25:01.934 Scheduled 86 items in 0.5 = 0.01 match + 0.53 place 2006-09-27 02:25:01.944 scheduler: Last message repeated 1 times: Finished recording: Future Fighting Machines: channel 1567 2006-09-27 02:25:01.935 Preview Error: Previewer file '/myth/tv/1567_20060927020000.mpg' is not valid. [mpeg2video @ 0xb6fff620]ac-tex damaged at 9 3 [mpeg2video @ 0xb6fff620]Warning MVs not available So looking at dmesg: Code: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. So searching for vmalloc, I found out that default setting for a normal kernel is 128m, so I added vmalloc=256m (my machine has 1GB of memory) to the append line in etc/lilo.conf and running lilo -v to update the boot files. I then rebooted and then commenced to schedule several simultaneous recordings to test it. The recordings were OK and the memory allocation error lines no longer appear. Hope this helps someone. Regards Bruce S.

Author:	tjc [ Thu Sep 28, 2006 8:31 pm ]
Post subject:
Nice catch!

Author:	cecil [ Mon Oct 02, 2006 9:49 pm ]
Post subject:
Nice indeed!

Author:	seano [ Wed Jan 03, 2007 10:00 pm ]
Post subject:	Re: Apparent fix for some zero length recordings on 5D1
bruce_s01 wrote: Hope this helps someone. Helped me! Thanks Bruce_s01! Only difference was: Code: kernel: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. Appeared in messages and kern.log (not in dmesg) Thanks again! -Seano

LinHES Forums http://forums.linhes.org/

Apparent fix for some zero length recordings on 5D1 http://forums.linhes.org/viewtopic.php?f=3&t=11875	Page 1 of 1

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/