[vdr] Re: VDR 1.3.15 gets unusable slow after a short time

[post <post@mhr.at>]

At 18:14 09.11.2004, you wrote:

> > I have no idea, what is going on here. This is my system:
> >
> > development-sources-2.6.8.1 (also tried 2.6.9 and 2.6.10_rc1) / Gentoo 
> Linux
> > - selected special kernel options:
> > - use register arguments
> > - message signaled interrupts (MSI and MSI-X)
> > - use 4kb for kernel stacks instead of 8 kb
> >
> > dvb-kernel that comes with kernel sources (also tried actual CVS)
> > NPTL enabled
> > glibc-2.3.4.20040808-r1
> > gcc-3.3.4-r1
> > one Hauppauge WinTV Nexus-S + CI-Slot-Adapter 545
> > one TechniSat SkyStar2 (also uses stv0299)
> > one Hauppauge WinTV analog-card
> >
> > Until now, I only installed vdr 1.3.15 (with a selfadapted vdr-1.3.14-r3
> > ebuild from gentoo.de) with the remote-plugin.
> >
> > When I start vdr, everything seems to be working fine. No abnormal messages
> > in /var/log/messages and no errors.
> >
> > After some time has passed, vdr seems to go to sleep. It still gives the
> > live-signal on the FF output, but it does not react on remote-keypresses.
> > In that state vdr is still running, and absolutely no error messages or
> > abnormalities in /var/log/messages.
> >
> > I just did the test: Pressing the MENU button, and waiting. Nothing
> > happens, looks like a complete ignore, live-signal still running on the FF
> > output. Finally the menu-screen comes up, about 5 MINUTES after the menu
> > key was pressed.
> >
> > What could be the problem?
> >
> > After a restart of vdr everything seems to be normal, but then suddently
> > that behaviour kicks in without further notice. All the rest on that
> > machine is running normally, I also have xorg-x11 + kde 3.3.1 installed,
> > and actually I am watching the live-signal on my monitor using kvdr.
>
> Could be the old NPTL problem.
>
> Try
>
>   export LD_ASSUME_KERNEL=2.4.1
>
> before running VDR.
I thought, the NPTL problem has already been fixes in 1.3.13 (I just 
searched the mailinglist-archive, I saw several success reports concerning 
a NPTL enabled system).

I even can not use that LD_ASSUME_KERNEL option:

linux # export LD_ASSUME_KERNEL=2.4.1
linux # /etc/init.d/vdr start
/sbin/runscript: error while loading shared libraries: libdl.so.2: cannot 
open s
hared object file: No such file or directory

and when I try to put it into the startscript before the final "su - vdr 
..." call:

 linux # /etc/init.d/vdr start
 * Re-caching dependency info (mtimes differ)...
 * Starting vdr (1.3.15) - The Video Disk Recorder...
su: error while loading shared libraries: libcrypt.so.1: cannot open shared 
object file: No such file or directory
 * Failed to start vdr.
/usr/bin/logger: error while loading shared libraries: libc.so.6: cannot 
open shared object file: No such file or directory       [ !! ]
rm: error while loading shared libraries: libc.so.6: cannot open shared 
object file: No such file or directory

When I just try to start it from the commandline without daemon mode, I 
just get:

/usr/bin/vdr: error while loading shared libraries: libpthread.so.0: cannot 
open shared object file: No such file or directory

What else could I try?

And can I savely assume, that the selected kernel options have nothing to 
do with this problem, as well as kernel-sources and dvb-sources selection?

The only possibility that comes to my mind at the moment, would be to unset 
the NPTL use flag, and recompile my whole system (it's not just done by 
recompiling glibc, I tried that yesterday, but KDE wouldn't start up any 
more, and also apache reported problems during boot).

BTW Klaus, I've read you use SuSe. Why don't you try Gentoo, that would 
give you an up to date system, and you could check all issues with a 
bleeding edge machine. I tried SuSe and RedHat in the past, but Gentoo 
definitely blows socks, it's THE metadistribution with all the choice you 
expect from Linux.

--
Sincerely,
Master One