On Sat, Apr 25, 2009 at 9:44 AM, John Lundell <[email protected]> wrote:
> On Sat, Apr 25, 2009 at 5:28 AM, Andy Walls <[email protected]> wrote: > >> On Thu, 2009-04-23 at 21:44 -0400, Andy Walls wrote: >> > On Thu, 2009-04-23 at 09:37 -0700, John Lundell wrote: >> > > Hi Andy >> > > >> > > I tried the cx18-perf branch to see if it would fix my minor problem >> > > when recording multiple streams (would occasionally drop a buffer when >> > > recording). This branch unfortunately made things much worse and has >> > > appears to have made my myth backend to crash three times in the last >> > > three days. >> > >> > Is this happening for analog captures, digital captures, or both with >> > the HVR-1600? >> > >> > Assuming this is happening for analog captures only, we may be running >> > into a BUG_ON() in the driver when reading a buffer and scheduling the >> > work object that the outgoing work handler is already acting upon. I >> > know what to do if this is the case. (I thought the kernel handled this >> > case gracefully, but I wasn't totally clear.) The "random" nature >> > sounds about right for this sort of race condition. >> > >> > >> > > I have two cards, one a HVR1600 and the other a DViCO FusionHDTV7 Dual >> > > Express. The problem seems to randomly happen with the HVR1600 HD >> > > tuner starts recording. It has a lower priority than the two DViCO HD >> > > tuners so it only kicks in occansionally. >> > > >> > > What can I do to help debug the problem? >> > >> > Hmmm. Could you please send the portions of the MythTV log at the time >> > of the capture and through the crash? I'd like to see what MythTV is >> > griping about. >> > >> > Also could you look for cx18 related messages in dmesg >> > or /var/log/messages for that same time period? >> > >> > Also, look for any "Oops" or "Bug" messages in the dmesg >> > or /var/log/messages, I'd like to see the complete dump from such a >> > message. >> > >> >> John, >> >> I'll have time to work on cx18 problems this evening (EDT). Could you >> provide some log output before then? >> >> Since this particular changeset is more complex than most, I'd like to >> get any problems debugged before I forget any nuances. I also know I >> have a time window tonight when the kids won't break my concentration >> every 5 minutes. :) >> >> Regards, >> Andy >> > > Hi Andy, > > Sure, I can try some tests this morning. > > John > > > Hi Andy, I ran a bunch of tests where I started and tuners recording and then started and stopped tuners one by one to see if I could get a crash and of course, observing the process makes it work, no crashes. I have attached the output from dmesg for two different tries. On the mythbackend crash log, there was nothing, just going to record program xyz and then nothing else. John
dmesg_org.tx.gz
Description: GNU Zip compressed data
dmesg.txt.gz
Description: GNU Zip compressed data
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
