Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24 - Linux-audio-dev

18 Nov 2003

On Tuesday 18 November 2003 20.57, 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) 
 OK, I tested it. There is no output at all from rt_monitor.
 I used the following:
 - starting rt_monitor in a console as root
 - ssh login from remote machine
 - starting jack
 - starting a jack client 
What client? Any client?

...

 after a few seconds the machine was froozen and no output
 from rt_monitor. 
Hmm...

...
  I assume its a hardware bug. On my Inspiron 8500 with
nearly
 the same linux-2.4.19.SuSE kernel (plus patch for speed-step)
 I dont have any freezes at all. 
But you do have it recompiled for the right CPU architecture
and not only moved?

BTW: There is a prefech bug on AMD processors - try to run it recompiled
with less optimization, newer kernels have workarounds.

Another thing to try is to run memtest86 (SuSE has it in Lilo menu)
let it run for a while (full night)

/RogerL

-- 
Roger Larsson
Skellefteå
Sweden