[mythtv-users] Mythbackend log:CC length(19) seq_num(0) 0xa 0x31 0x98 0x3b 0xcf 0x0 0x61 0x1f 0x10 0x90 0x5 0x3 0x91 0x3f 0x0 0x3f 0x92 0x1
digitalaudiorock at gmail.com
Sat Jul 31 19:46:03 UTC 2010
On Sat, Jul 31, 2010 at 1:54 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 07/31/2010 11:04 AM, Tom Dexter wrote:
>> On Wed, Jul 28, 2010 at 10:18 PM, Daniel Kristjansson wrote:
>>> On Wed, 2010-07-28 at 21:08 -0400, Steven Adeff wrote:
>>>> anyone know what's causing this? something I need to be concerned with?
>>>> CC length(19) seq_num(0) 0xa 0x31 0x98 0x3b 0xcf 0x0 0x61 0x1f 0x10
>>>> 0x90 0x5 0x3 0x91 0x3f 0x0 0x3f 0x92 0x1
>>> No, just debugging. It shouldn't be printed out unless you enable
>>> some verbose output, but even if improperly printed it is no cause
>>> for alarm
>> I have a question relating to this. I'm still running 0.22. I've had
>> a few bad recordings lately...I think one of my HD-5500 cards might be
>> either going or poorly seated or something.
>> The commflagging attempt on the backend really hammered my logs with
>> ffmpeg decode errors. My mythbackend runs with "important,general".
>> Shouldn't I only get those with libav enabled?
> No. Anything that ffmpeg treats as an error (versus a warning) will be
> logged at important verbosity.
> http://svn.mythtv.org/trac/ticket/6729 has some info, but if you truly want
> to ignore the messages, you'll likely have to just comment out the message
> in the source.
Thanks! Yea that makes sense. They shouldn't really occur to any
significant extent under normal conditions anyway. As a matter of
fact, in this particular case, it was one of my three HD-5500 cards
going south. I noticed that both failed recordings were on the same
card, and then noticed I was getting these in /var/log/messages:
Jul 31 12:14:00 mythback kernel: tda9887 1-0043: i2c i/o error: rc ==
-6 (should be 4)
As a matter of fact, today it had gotten to the point were I couldn't
get better than about 55% signal on it (even when switching around
antenna cables). I finally started getting more of the above syslog
errors and they were actually making the system almost unresponsive.
I pulled out that card and all is well until I can get a new one.
More information about the mythtv-users