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. -Mike _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
