Kovacs Balazs wrote: > > Holger Waechtler wrote: > > > > Kovacs Balazs wrote: > > > I've found a problem (maybe bug) with HEAD driver (maybe it causes the > > > mplayer bugs also) > > > > it's not a bug, it's the not-disabled-powermanagement. See below. > > > > > When I don't attach an antenne to the DVB card, and start HEAD driver, > > > and after that I start an application which want to tune to a channel, > > > kdvb-fe proccess starts to eat my CPU time, and even after quitting the > > > application which want to tune (dvbtune, scan, vdr ....) the kdvb-fe > > > still eats CPU time, (~50% on my C766) until I restart the driver. > > > > remove the "dvb_shutdown_timeout=0" module parameter from your Makefile > > when insmod'ing the driver or pass a timeout value > 0 to the dvb-core > > module. > > > > Then the kdvb-fe thread will exit after a few seconds and won't try to > > to catch a transponder anymore. > > thanks, you're right, it works. when i start vdr it wants to tune a > channel, and kdvb-fe process starting and eating 40-50% of cpu time, but > f.e. mplayer works fine meanwhile. > > kdvb-fe thread active until vdr runs and eats CPU time (I checked with > top) , but if I quit vdr kdvb-fe thread exists and free up CPU.
Holger, I have realized that, when I start mplayer from VDR, it eats the CPU. Only thing that changed with starting driver without "dvb_shutdown_timeout=0" that if VDR quit, kdvb-fe process disappear, and won't eat CPU time after. From command line mplayer works OK. I think this is because VDR wants to tune a channel with the driver, and the driver starts to eat my CPU. Is there any solution? thanks basq -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
