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 > If nothing's obvious after looking at all that, we'll starting turning > on extra logging from the cx18 driver with the "debug=..." module > parameter. > > $ modinfo cx18 > [...] > parm: debug:Debug level (bitmask). Default: 0 > 1/0x0001: warning > 2/0x0002: info > 4/0x0004: mailbox > 8/0x0008: dma > 16/0x0010: ioctl > 32/0x0020: file > 64/0x0040: i2c > 128/0x0080: irq > 256/0x0100: high volume > [...] > > We'll probably be interested in info, warning, mailbox, dma, file, and > irq (debug=175) and maybe with high volume turned on (debug=431) but the > log file will be enormous in that case. > > Regards, > Andy > > > John > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
