[mythtv-users] FC5 crashing with newly installed 0.20

[Jay Bradley]

I'm still having this problem but have switched to just using 
mythfilldatabase. I am also using atrpms and yum a Nova-T PCI card and FC5.

mythbackend --version
Library API version: 0.20.20060828-3
Source code version: Unknown
Options compiled in:
 linux release using_xvmcw using_lmsensors using_v4l using_oss 
using_alsa using_arts using_jack using_ivtv using_firewire using_dbox2 
using_hdhr using_ip_rec using_freebox using_live using_lirc 
using_joystick_menu using_dvb using_x11 using_xv using_xrandr using_xvmc 
using_xvmc_vld using_opengl_vsync using_opengl using_frontend using_backend


Jay

Brad DerManouelian wrote:
> On Oct 20, 2006, at 1:06 AM, Jonas Anden wrote:
>
>   
>> Hi Jay (and everyone else listening),
>>
>> I know it was a while ago since you mailed out about your problems  
>> with
>> mythbackend crashing during EIT scanning. Did you get these problems
>> resolved? If so, how? If not, what DVB card(s) are you using?
>>     
>
> I'm still having this problem with my HD-5500 card, but I'm not  
> running SVN. I'm using ATrpms:
> [mythtv at mythtv ~]$ mythbackend --version
> Library API version: 0.20.20060828-3
> Source code version: Unknown
>
>   
>> I think I've got the same issue with my Nova-T 500 (DVB-T dual tuner).
>> It is a PCI board with an on-board USB controller attached to two  
>> DiBcom
>> 0700 tuner chips.
>>
>> I have noticed that during these crashes when myth is scanning for EIT
>> data, it does not seem to close all demuxers, and when the number of
>> open file handles related to the tuner chip reaches 22, the card seems
>> to do a USB disconnect/reconnect, which in turn causes an kernel Oops
>> (since the dvb-usb drivers don't handle USB disconnection while it is
>> "in use"). I don't know if this is a fault management operation, or if
>> it is some kind of buffer overrun that causes the disconnection  
>> (haven't
>> looked at the code yet). Sometimes this results in the box freezing  
>> up,
>> sometimes it just goes on but can't record DVB (which is worse, since
>> the scheduler then does not take action to reschedule the shows using
>> the analog tuners on my primary backend).
>>
>> Looking at open files while running, mythbackend is using the frontend
>> constantly. I have two tuners, so I see /dev/dvb/adapter0/frontend0
>> and /dev/dvb/adapter1/frontend0. When a recording starts, mythbackend
>> uses 7 open files for this -- 1 for frontend0, 1 for 'dvr0', and 5(!)
>> for the demux0 device. The EIT scanner does this similarly, but when
>> done it does not always close the demux0 device, leaving them open  
>> after
>> the operation has completed.
>>
>> I'll take a look at the code for the EIT scanning this weekend to  
>> see if
>> I can spot what is leaving the demux0 device open.
>>
>>   // J
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>>     
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>