The messages (of which no doubt there are gazillions)
can be prevented by upgrading to ivtv 0.4.2 or higher.
--- Chris Hembrow <[EMAIL PROTECTED]>
wrote:
> Hi
>
> a couple of times now, my mythtv box (combined
> back/frontend) has
> locked up. I'm running FC4 as per Jarods guide. The
> hard driv
Hi
a couple of times now, my mythtv box (combined back/frontend) has
locked up. I'm running FC4 as per Jarods guide. The hard drive
activity starts going crazy, and the box stops responding to any
input. This happened this evening, and 2 recordings stopped at 21:46.
I rebooted the box and checked
[EMAIL PROTECTED] wrote:
>On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote:
>
>
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
#2:
Stealing a Buf
fer, 512 currently allocated
>>More memory does not appear to help. Did anyone ma
Niels den Otter wrote:
>Al,
>
>Al McIntosh wrote:
>
>
>>The last few occurances have been in the evening or night.
>>
>>mythfilldatabase has been running around 11am.
>>
>>I do have mythcommflag set to run when the recording starts.
>>
>>
>
>Are you using MythTV SVN? I had a similar problem
Niels den Otter wrote:
>Al,
>
>Al McIntosh wrote:
>
>
>>The last few occurances have been in the evening or night.
>>
>>mythfilldatabase has been running around 11am.
>>
>>I do have mythcommflag set to run when the recording starts.
>>
>>
>
>Are you using MythTV SVN? I had a similar problem
Al,
Al McIntosh wrote:
> The last few occurances have been in the evening or night.
>
> mythfilldatabase has been running around 11am.
>
> I do have mythcommflag set to run when the recording starts.
Are you using MythTV SVN? I had a similar problem recently (after LiveTV
changes) which was sol
> Keith C wrote:
>
>> On Dec 15, 2005, at 3:41 AM, Marius Schrecker wrote:
>>
>>> Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
>>> #2:
>>> Stealing a Buf
>>> fer, 512 currently allocated
>>
>>
>> This means the client app is not pulling data fast enough from the
>> driver b
[EMAIL PROTECTED] wrote:
On Sun, Jan 08, 2006 at 08:23:52PM -0500, Al McIntosh wrote:
Interesting, I have a rather fast mythbox, AMD 2800+ with 1G ram and a
single pvr250. The buffer overflow often occurs in the middle of the
night when the only load on the machine is mythbackend recording
Endaf Jones wrote:
On 1/8/06, Al McIntosh <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote:
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
#2:
Stealing a Buf
fer, 512 currently allocated
On 1/8/06, Al McIntosh <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
> >On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote:
> >
> >
> Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
> #2:
> Stealing a Buf
> fer, 512 currently allocated
>
On Sun, Jan 08, 2006 at 08:23:52PM -0500, Al McIntosh wrote:
> Interesting, I have a rather fast mythbox, AMD 2800+ with 1G ram and a
> single pvr250. The buffer overflow often occurs in the middle of the
> night when the only load on the machine is mythbackend recording.
Does it happen at the
[EMAIL PROTECTED] wrote:
On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote:
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
#2:
Stealing a Buf
fer, 512 currently allocated
More memory does not appear to help. Did anyone manage a fix for this?
On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote:
> >>Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
> >>#2:
> >>Stealing a Buf
> >>fer, 512 currently allocated
>
> More memory does not appear to help. Did anyone manage a fix for this?
In my case, it turned out
Keith C wrote:
On Dec 15, 2005, at 3:41 AM, Marius Schrecker wrote:
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW
#2:
Stealing a Buf
fer, 512 currently allocated
This means the client app is not pulling data fast enough from the
driver buffer and you could loose s
Im running on 2 Gigs of dual channel memory so don't think that's the
problem ;) will watch the list for a good time to recompile from svn :-)
I also have a considerable amount of ram and disk space on my myth only
system and see similar similar behaviour.
My mythbackend system became
> On Dec 15, 2005, at 3:41 AM, Marius Schrecker wrote:
>
>> Anyone seen this in dmesg:
>>
>> Wondering if it has something to do with my flickering problems:
>
> Probably, yes.
>
>>
>> Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0
>> OVERFLOW #2:
>> Stealing a Buf
>> fer, 512 currentl
On Dec 15, 2005, at 3:41 AM, Marius Schrecker wrote:
Anyone seen this in dmesg:
Wondering if it has something to do with my flickering problems:
Probably, yes.
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0
OVERFLOW #2:
Stealing a Buf
fer, 512 currently allocated
This mea
Anyone seen this in dmesg:
Wondering if it has something to do with my flickering problems:
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW #2:
Stealing a Buf
fer, 512 currently allocated
Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW #0:
Stealing a Buf
18 matches
Mail list logo
