18 Nov
2003
18 Nov
'03
8:29 a.m.
BUT, I think a userspace daemon that starts at boot
time and protects
against lockups (rt_monitor) would be a very good thing to have.
Yes indeed, but on my XP machine which freezes after a few seconds
after a client had connected to jack even rt_monitor did not helped,
the machine keeped totally locked. Ping is still answered but thats it.
- Stefan
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
18 Nov
18 Nov
1:04 p.m.
New subject: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24
On Tuesday 18 November 2003 13.28, Stefan Nitschke wrote:
ping is answered = IRQs live.
Could you please try this.
Start rt_monitor in a text console CTRL-ALT-F1
Start your client, return to console - what does rt_monitor print?
(It could be the memory leak and mlockall(FUTURE) problem,
As I do not check that yet.
Another alternative is a fast forking client - they are hard to stop)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
BUT, I think a
userspace daemon that starts at boot time and protects
against lockups (rt_monitor) would be a very good thing to have.
Yes indeed, but on my XP machine which freezes after a few seconds
after a client had connected to jack even rt_monitor did not helped,
the machine keeped totally locked. Ping is still answered but thats it.
7668
days inactive
7668
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Roger Larsson -
Stefan Nitschke