Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat +preempt + alsa + jack = dead computer

2002-12-07 Thread Paul Davis
Are you certain your freeze is actually happening in kernel space? 
Tried using watchdog with ping-pong between highest and lowest 
priority SCHED_FIFO threads? (BTW, we should have a watchdog anyway, 
probably integrated with givertcap or something.)

JACK has its own watchdog thread. if engine-watchdog_check isn't
reset periodically, it will shut down the entire thing. or rather, it
will try to. the problem is that i'm not sure that its method of doing
so is particularly accurate, and moreover, the thing that is hogging
the CPU may be an out-of-process client, in which case shutting down
jackd doesn't help matters. this needs fixing. we should use:

  kill (SIGKILL, current_client);
  kill (SIGKILL, -1); // kill entire process group of JACK
  

--p



Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat +preempt + alsa + jack = dead computer

2002-12-06 Thread Fernando Pablo Lopez-Lezcano
 Fernando Pablo Lopez-Lezcano wrote:
 
  Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
  fine. I probably should post to the lkml with as much detail as we can 
  get (unless some kernel hacker is actually reading these messages). 
 
 I've tried every kernel from 2.4.20-pre5 up to 2.4.20-pre10, and again
 2.4.20-pre10-ac3, which caused a lockup on my system in the past, this
 afternoon. And I couldn't reproduce even _one_ lockup. I use another IDE
 interface though: a cmd649 add-on controller. The lockups happened with
 the onboard IDE interface (VIA KT333 chipset, vt8235 southbridge).

To add one more datapoint to the thread and (apparently good news): I'm
testing 2.4.20 (final) + lowlat + preempt + acpi + alsa + jack and the
computer seems to be chugging along nicely. This is with today's alsa. A
slighly older alsa did lock the computer after 5 or so minutes of jack
activity but I managed to reboot it with the sysrq magic key. With the
newest alsa I got jack + freqtweak + ams (with the demo patch) running
for 50 minutes until for some reason jack died due to a watchdog
interrupt. Not bad. 

-- Fernando





Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat + preempt + alsa + jack = dead computer

2002-11-04 Thread Stefan Schwandter
Fernando Pablo Lopez-Lezcano wrote:

 Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
 fine. I probably should post to the lkml with as much detail as we can 
 get (unless some kernel hacker is actually reading these messages). 

I've tried every kernel from 2.4.20-pre5 up to 2.4.20-pre10, and again
2.4.20-pre10-ac3, which caused a lockup on my system in the past, this
afternoon. And I couldn't reproduce even _one_ lockup. I use another IDE
interface though: a cmd649 add-on controller. The lockups happened with
the onboard IDE interface (VIA KT333 chipset, vt8235 southbridge).

For now I'm too lazy to open the computer case and try with the VIA
interface to be sure, but... I can't think of another change to my
system, so maybe that's the reason for the lockups. What IDE interface
do you have?


regards, Stefan
-- 
 http://www.shockfrosted.org



Re: [Jackit-devel] Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 +lowlat + preempt + alsa + jack = dead computer

2002-11-04 Thread Fernando Pablo Lopez-Lezcano
 Fernando Pablo Lopez-Lezcano wrote:
 
  Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
  fine. I probably should post to the lkml with as much detail as we can 
  get (unless some kernel hacker is actually reading these messages). 
 
 I've tried every kernel from 2.4.20-pre5 up to 2.4.20-pre10, and again
 2.4.20-pre10-ac3, which caused a lockup on my system in the past, this
 afternoon. And I couldn't reproduce even _one_ lockup. I use another IDE
 interface though: a cmd649 add-on controller. The lockups happened with
 the onboard IDE interface (VIA KT333 chipset, vt8235 southbridge).
 
 For now I'm too lazy to open the computer case and try with the VIA
 interface to be sure, but... I can't think of another change to my
 system, so maybe that's the reason for the lockups. What IDE interface
 do you have?

I tried 2.4.20rc1 on a laptop and lspci says:
  IDE interface Intel Corp. 82801CA IDE U100 (rev 02)
and on an hp desktop (old...):
  IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)

I'll try again latter on different machines...
-- Fernando




Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat + preempt + alsa + jack = dead computer

2002-11-03 Thread Fernando Pablo Lopez-Lezcano
 Fernando Pablo Lopez-Lezcano wrote:
 
  If I start jackd and then use the freqtweak jack client I get a completely
  dead machine in a very short time (from a few seconds to 10 or 20
  seconds).
 
  [...]
 
 I get exactly the same results as you. 2.4.19 works fine,
 2.4.20-pre10-ac3, 2.5.41 - 2.5.45 lock up.

Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
fine. I probably should post to the lkml with as much detail as we can 
get (unless some kernel hacker is actually reading these messages). 

-- Fernando




Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat + preempt + alsa + jack = dead computer

2002-11-03 Thread Stefan Schwandter
Fernando Pablo Lopez-Lezcano wrote:

 Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
 fine. I probably should post to the lkml with as much detail as we can 
 get (unless some kernel hacker is actually reading these messages). 

Hmm, it's actually pre10-ac2, there hasn't been an -ac3 yet :-) But to
answer your question: yes, I've tried various other 2.4.20 prepatches,
but I don't know exactly which ones. All of them had the lockup problem
however.


regards, Stefan



Re: [linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat + preempt + alsa + jack = dead computer

2002-11-03 Thread Stefan Schwandter
Fernando Pablo Lopez-Lezcano wrote:

 Have you tried anything in between pre10-ac3 and pre4? I know pre4 works 
 fine. I probably should post to the lkml with as much detail as we can 
 get (unless some kernel hacker is actually reading these messages). 

Does it fail with 2.4.20-pre5? I've found a changelog entry for pre5
that looks like it might have something to do with the problem.

[EMAIL PROTECTED]:
  o Fix scheduler's RT behaviour
  
regards, Stefan
-- 
 http://www.shockfrosted.org



[linux-audio-dev] Re: [Jackit-devel] 2.4.20-rc1 + lowlat + preempt + alsa + jack = dead computer

2002-11-02 Thread Stefan Nitschke
From: Fernando Pablo Lopez-Lezcano [EMAIL PROTECTED]
Is anyone out there trying out this combination?:

  kernel 2.4.20-rc1
  capabilities patch
  low latency patch
  preemptible kernel patch
  almost current alsa cvs [20021028.170432 usa pacific time]

If I start jackd and then use the freqtweak jack client I get a completely
dead machine in a very short time (from a few seconds to 10 or 20
seconds).

...

Interestingly enough just the jack server running is not enough to kill
the machine. Adding a jack client (just tried alsaplayer, same problem as
freqtweak) kills the machine really fast.



I have excactly the same problem since i upgraded my machine to SuSE 8.0,
which is based on: kernel 2.4.19-SuSE + capabilities patch + low latency
patch.

Stefan


_
Surf the Web without missing calls! Get MSN Broadband. 
http://resourcecenter.msn.com/access/plans/freeactivation.asp