> Mike wrote:
>
>>I have the same issue but I think it happens to me when mysql corrupts a
>>table 'recordedmarkup'. (causing the system to go nuts) I believe my
>>corruption issue might be related to my northbridge fan going out and
>>possibly causing the system to reboot mid stride from overheating or
>>something. I just replaced it a few mins ago to figure out if this is
>>whats causing it. But I guess there is always the possiblity that this
>>error message is bogging down the system so much that it is the cuprit
>>but thats not what i'm thinking right now.
>>
>>All I know is this system used to stay up for months on end without any
>>problems. Since I've moved away from 0.3.8 it has been flakey to say the
>>least. But I think my problems is probably due to the problem stated
>>above. I will wait and see I guess, if not I'm going to have to decide
>>if mythtv cares if I switch them to InnoDb over MyISAM. I have little
>>faith in MyISAM on large tables from past experience anyways so I'd
>>really prefer the switch either way. But thats my next step before I
>>decide that its ivytv.
>>
>>Anywho, that error message needs to be supressed somehow. Currently I'm
>>waiting around for the hundreds of megs of that log to roll off from the
>>last time it happened.
>>
>>-Mike
>>
>>
>
> Well scratch that. All I can think of now is that its ivytv somehow...
> The thing is just totally unusable because of whatever its doing when it
> logging all of this crap. I tripled the memory thinking that might be
> it, switched out all of the fans and half of the hardware.
>
> I guess i'm just going to have to go back on the drivers to see if I can
> use it again. At this point, all this thing does is log those errors and
> screws up all of the recordings. After a good solid year of it working
> decently well.
These errors mean that the reader (MythTV in this case) is not reading or
reading too slow, so the ivtv buffer become full. It is true that it would
be nice if ivtv would show this message only once but changing that will
not fix the problem.
The guys over at the pvrusb2 mailinglist seem to have similar problems. To
me it looks like a change in MythTV causes this. Whether this is a MythTV
problem or an ivtv problem (possibly something that is triggered by a
MythTV change) is something someone should investigate.
It is all very well if people tell one another that it doesn't work (Mike,
don't take this personally, it is a general comment) but it is much better
if someone would actually start to debug what is going on. I simply don't
have the time and since I don't use MythTV I am also not the best person
to debug it.
Come on people, there must be someone who can look into this?
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
