Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] issues with receiver thread
- To: vdr@linuxtv.org
- Subject: [vdr] issues with receiver thread
- From: Michael Reinelt <reinelt@eunet.at>
- Date: Sat, 28 Jun 2003 09:29:40 +0200
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset=ISO-8859-15; format=flowed
- Organization: netWorks
- Reply-to: vdr@linuxtv.org
- Sender: vdr-bounce@linuxtv.org
- User-agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.3) Gecko/20030312
Hi there,
I'm using VDR since two months, and I'm basically very happy with it.
Congratulations for this fine program!
But there are some issues which I'd like to solve, I debugged a bit in
the code, and found that the cause is the receiver thread.
I'm running VDR on a disk- and fanless EPIA-M6000 with PXELINUX and
nfsroot. This works fine.
When I boot the box, after initialisation the load average is nearly
0.0, CPU temperature is about 57°C, and the box consumes about 30W.
As soon as I start a recording, load rises to 0.20, CPU temperature to
64°C, 37 W, which is what I would expect.
But when the recording is finished, the values stay at these levels! I
have to restart VDR to get the initial low values.
I found out that the receiver thread uses the CPU regularly (about
5-15%). The reason why the receiver thread does not exit is the transfer
thread, which does not consume any CPU time. I couldn't find out why the
transfer thread does not end after recording.
The running receiver thread has another side effect: The EPG scan will
not run, because of the following line in eitscan.c:
if (!(Device->Receiving(true) || Device->Replaying())) {
// scan transponders
}
This is really annoying, because my box runs 24h, and the other day I
don't have EPG data for some channels (e.g. ARD or WDR, the EPG data for
these channels cover only a short period). As I'm using vdradmin and its
autotimers, these things wont work without valid EPG data.
There's another side-effect with the receiver thread: The (OSD) teletext
plugin. As far as I understood, this plugin starts a receiver thread,
too, which has the issues described above. Especially the teletext
plugin would profit from the EPG scan: Teletext information would be
updated, too.
I've seen that there's some kind of "priority" in the Device:Receiving()
method, but I don't understand the logic behind. Maybe the teletext
plugin should set a very low priority, and these low priority receivers
should not be checked?
Any hints? Comments?
TIA, Michael
--
netWorks Vox: +43 316 698260
Michael Reinelt Fax: +43 316 692343
Geisslergasse 4 GSM: +43 676 3079941
A-8045 Graz, Austria e-mail: reinelt@eunet.at
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index