[vdr] VDR gets somehow stuck and consumes all CPU time

Paavo Hartikainen pahartik at sci.fi
Mon Dec 5 03:57:02 CET 2005


Johannes Stezenbach <js at linuxtv.org> writes:

> The patch below might help, gettid() returns the PID of the
> thread. (And since it's a syscall it is independent of NPTL
> vs. linuxthreads. Tested on 2.6 only, but the gettid man page says
> it's available in 2.4.20.  gettid() is Linux specific.)

Before patch:
---
Dec  3 05:27:30 sarabi vdr[22722]: tuner on device 1 thread started (pid=22722, tid=822543584)
Dec  3 05:27:32 sarabi vdr[22722]: tuner on device 2 thread started (pid=22722, tid=814154976)
---

After patch:
---
Dec  5 04:31:46 sarabi vdr[27624]: tuner on device 1 thread started (pid=27624, tid=-1)
Dec  5 04:31:48 sarabi vdr[27624]: tuner on device 2 thread started (pid=27624, tid=-1)
---

After patch and "env LD_ASSUME_KERNEL=2.4.1":
---
Dec  5 04:35:01 sarabi vdr[27641]: tuner on device 1 thread started (pid=27641, tid=-1)
Dec  5 04:35:03 sarabi vdr[27644]: tuner on device 2 thread started (pid=27644, tid=-1)
---

I assumed that "make clean" is not required after patching, just
"make".

Now just waiting for threads to get wildly active.

-- 
 "pienena   /  Paavo "Rainbow Rat" Hartikainen
  minusta  /  E-mail: pahartik at sci.fi
  tulee   /  URL: http://www.sci.fi/~pahartik/
  rotta" /  EFnet: pahartik at #Atari and #LionKing



More information about the vdr mailing list