ALSA + jack + xrun = kernel crash
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens when jackd xruns. I've been reproducing it using "jackd -d alsa" (other options don't make a difference) then "ladccad". Once the system crashs the only way to get any responce is with SysRq. Keys don't echo to the console and I can't switch VTs.
Generally there is no error message or oops that I can see, even when debug=full is enable in ALSA. Early on I saw a message from jackd to the tune of "error write 512 somethings to device", but I have not been able to reproduce it. I am willing to run any tests that might help. I use journaling filesystems ;-)
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.
SoundBlaster Live! Value
ATI Radeon 8500 (using the closed-source ATI drivers; version 2.9.8)
My software is:
ALSA drivers 0.9.3a or current CVS
Linux 2.4.20 (vanilla or gentoo patched) Jack 0.71.2
Current Gentoo with testing packages enabled (~x86)
Thanks.
-Arthur
PS: I have sporadic hard freezes when I use Xv heavily and I had to lower the AGP rate from 4x to 2x to prevent a crash when my X server loaded. This is just in case it might be related. It could be my MB I guess. [shiver]
Signature · 9 lines
Arthur Peters <[email protected]> ------------------------------------------------------- This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Quoted 2 lines
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens
[ ... ]
Quoted 2 lines
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.
[ .... ]
Quoted 2 lines
My software is:
ALSA drivers 0.9.3a or current CVS
current CVS (and presumably 0.9.3a) has a severe bug with SMP systems. i reported it last week, along with as much output as i could get from my machine when it locked up. nobody has been able to do anything about it since then.
you will need to back to the cvs snapshot of april 27th to get a working version for SMP systems.
jaroslav or takashi - any ideas about fixing this?
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
Quoted 14 lines · Paul Davis
Quoted 2 lines
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens
[ ... ]
Quoted 2 lines
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.[ .... ]
Quoted 2 lines
My software is:
ALSA drivers 0.9.3a or current CVScurrent CVS (and presumably 0.9.3a) has a severe bug with SMP systems. i reported it last week, along with as much output as i could get from my machine when it locked up. nobody has been able to do anything about it since then.
Quoted 4 lines
you will need to back to the cvs snapshot of april 27th to get a working version for SMP systems.
jaroslav or takashi - any ideas about fixing this?
Paul, could you, please, enable spinlock debug in your SMP kernel?
include/linux/spinlock.h:
#define DEBUG_SPINLOCKS 0 /* 0 == no debugging, 1 == maintain lock state, 2 == full debug */
Use full debug. I am sorry, but I have not a SMP machine around.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
I tried this, but I didn't get any additional output. I looked at include/linux/spinlock.h and it appears that the line you are refering to only affects UP compiles. This explains why I didn't get any output.
Am I doing something wrong? Anything else I could do to help?
-Arthur
Quoted 10 lines · Jaroslav Kysela
Paul, could you, please, enable spinlock debug in your SMP kernel?
include/linux/spinlock.h:#define
DEBUG_SPINLOCKS0 /* 0 == no debugging, 1 == maintain lock state, 2 == full debug */Use full debug. I am sorry, but I have not a SMP machine around.
Jaroslav
Signature · 9 lines
Arthur Peters <[email protected]> ------------------------------------------------------- This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
At Sat, 17 May 2003 08:27:29 -0400,
Quoted 15 lines · Paul Davis
Quoted 3 lines
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens
[ ... ]
Quoted 2 lines
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.[ .... ]
Quoted 2 lines
My software is:
ALSA drivers 0.9.3a or current CVScurrent CVS (and presumably 0.9.3a) has a severe bug with SMP systems. i reported it last week, along with as much output as i could get from my machine when it locked up. nobody has been able to do anything about it since then.
Quoted 4 lines
you will need to back to the cvs snapshot of april 27th to get a working version for SMP systems.
jaroslav or takashi - any ideas about fixing this?
it's likely spin dead locks, but it's difficult to guess where this happens.
after auditing the new codes, i fixed some possible dead locks. most of the fixed places, however, happen in suspend/resume conditions or timeout after 10sec, so this unlikely fixes your case.
could you check whether snd_pcm_stream_linked() returns really only zero? if yes, the code path shouldn't include the complicated locks in snd_pcm_action_group(), and it will narrow the possible bugggy points much...
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
Quoted 2 lines
could you check whether
snd_pcm_stream_linked()returns really only zero? if yes, the code path shouldn't include the complicated locks
aw shoot. of course it returns true: jack tries to link capture+playback so that we only have to issue single commands to start+stop. damn, i forgot that, sorry.
--p
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
Quoted 8 lines
aw shoot. of course it returns true: jack tries to link capture+playback so that we only have to issue single commands to start+stop. damn, i forgot that, sorry.
One thing that would be interesting to known more about is why does jack not the hangup the machine at once when I start it without the "-R" flag. (wich will results in a lot more xruns)
Without the "-R" flag: (almost all the times ...)
- jackd runs without locking up the machine
until I try to connect any client.
- after stopping jackd (Ctrl-C) without conecting any client,
the machine dont behave correctly after this, for example
when a 'A' key in the terminal I got any other character, programs does not start correctly, the machine does not shutdown
correctly, but have not seen any "oops" (but maybe just a random coincidence ....)
But if it's a spin_lock(...) problem why does not just lock up my machine in this case ?
I would interesting to known what happens if someone else could try starting the jackd without the "-R" and latest ALSA CVS. (on a SMP machine .. -;)
/Benny
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
At Mon, 19 May 2003 12:38:14 -0400,
Quoted 7 lines · Paul Davis
Quoted 3 lines
could you check whether
snd_pcm_stream_linked()returns really only zero? if yes, the code path shouldn't include the complicated locksaw shoot. of course it returns true: jack tries to link capture+playback so that we only have to issue single commands to start+stop. damn, i forgot that, sorry.
ok, i found a serious typo in pcm_native.c, which i guess as the culprit.
could you try the cvs version?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Ok, second try:
alsa 0.9.3c fresh from CVS
---------------------------------------
/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 0.9.3c. Compiled on May 21 2003 for kernel 2.4.20-LL with versioned symbols.
/proc/asound/cards:
0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1371 at 0xb000, irq 5
---------------------------------------
jack 0.71.2 fresh from CVS
spiralsynthmodular
the first error:
jack -R -d alsa (as root)
---------------------------------------
jackd 0.71.2
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support
loading driver ..
creating alsa driver ... default|1024|2|48000|swmon|swmeter|rt open
You appear to be using the ALSA software "plug" layer, probably a result of using the "default" ALSA device. This is less efficient than it could be. Consider using a ~/.asoundrc file to define a hardware audio device rather than using the plug layer
You appear to be using the ALSA software "plug" layer, probably a result of using the "default" ALSA device. This is less efficient than it could be. Consider using a ~/.asoundrc file to define a hardware audio device rather than using the plug layer
port alsa_pcm:capture_1 has mixdown = 0x4003410e
port alsa_pcm:capture_2 has mixdown = 0x4003410e
port alsa_pcm:playback_1 has mixdown = 0x4003410e
port alsa_pcm:playback_2 has mixdown = 0x4003410e
starting engine
**** alsa_pcm: xrun of at least 78.613 msecs
**** alsa_pcm: xrun of at least 0.194 msecs
**** alsa_pcm: xrun of at least 0.030 msecs
**** alsa_pcm: xrun of at least 0.025 msecs
port SSM:In0 has mixdown = 0x4003410e
port SSM:In1 has mixdown = 0x4003410e
port SSM:In2 has mixdown = 0x4003410e
port SSM:In3 has mixdown = 0x4003410e
port SSM:In4 has mixdown = 0x4003410e
port SSM:In5 has mixdown = 0x4003410e
port SSM:In6 has mixdown = 0x4003410e
port SSM:In7 has mixdown = 0x4003410e
port SSM:Out0 has mixdown = 0x4003410e
port SSM:Out1 has mixdown = 0x4003410e
port SSM:Out2 has mixdown = 0x4003410e
port SSM:Out3 has mixdown = 0x4003410e
port SSM:Out4 has mixdown = 0x4003410e
port SSM:Out5 has mixdown = 0x4003410e
port SSM:Out6 has mixdown = 0x4003410e
port SSM:Out7 has mixdown = 0x4003410e
could not complete playback of 1024 frames
cycle execution failure, exiting
telling signal thread that the engine is done
jack main caught signal 1
---------------------------------------
no problem up to this point (but for the fact that jack terminates)
Then I try to restart jack with the same command. It starts, but after the second xrun it hangs the system.
Pieter
Quoted 22 lines · Takashi Iwai
At Mon, 19 May 2003 12:38:14 -0400,
Quoted 9 lines · Paul Davis
Quoted 4 lines
could you check whether
snd_pcm_stream_linked()returns really only zero? if yes, the code path shouldn't include the complicated locksaw shoot. of course it returns true: jack tries to link capture+playback so that we only have to issue single commands to start+stop. damn, i forgot that, sorry.
ok, i found a serious typo in
pcm_native.c, which i guess as the culprit.
could you try the cvs version?Takashi
Quoted 12 lines
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
At Wed, 21 May 2003 02:32:02 +0200,
Quoted 9 lines · Pieter Palmers
Ok, second try:
alsa 0.9.3c fresh from CVS
---------------------------------------
/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 0.9.3c. Compiled on May 21 2003 for kernel 2.4.20-LL with versioned symbols.
Quoted 5 lines
/proc/asound/cards:0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI Ensoniq AudioPCI ENS1371 at 0xb000, irq 5 ---------------------------------------
how about this one? this should fix another deadlock (including the simplified expression of stream lock)
Takashi
Quoted 11 lines · Takashi Iwai
At Wed, 21 May 2003 02:32:02 +0200,
Quoted 9 lines · Pieter Palmers
Ok, second try:
alsa 0.9.3c fresh from CVS
---------------------------------------
/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 0.9.3c. Compiled on May 21 2003 for kernel 2.4.20-LL with versioned symbols.
Quoted 8 lines
Quoted 5 lines
/proc/asound/cards:0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI Ensoniq AudioPCI ENS1371 at 0xb000, irq 5 ---------------------------------------how about this one? this should fix another deadlock (including the simplified expression of stream lock)
Takashi, the self_group is designed to avoid mess in the lowlevel drivers. Now, the code is same for both linked and standalone streams. Please, do not remove it.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
At Wed, 21 May 2003 13:35:39 +0200 (CEST),
Quoted 18 lines · Jaroslav
Quoted 15 lines · Takashi Iwai
At Wed, 21 May 2003 02:32:02 +0200,
Quoted 13 lines · Pieter Palmers
Ok, second try:
alsa 0.9.3c fresh from CVS
---------------------------------------
/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 0.9.3c. Compiled on May 21 2003 for kernel 2.4.20-LL with versioned symbols.
/proc/asound/cards:
0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCIEnsoniq AudioPCI ENS1371 at 0xb000, irq 5
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
---------------------------------------how about this one? this should fix another deadlock (including the simplified expression of stream lock)
Takashi, the
self_groupis designed to avoid mess in the lowlevel drivers.
which mess do you mean?
as far as i see, only self_group.lock is used in the code. (so i replaced self_group with a single spinlock.)
Quoted 2 lines
Now, the code is same for both linked and standalone streams. Please, do not remove it.
ok.
meanwhile, i committed my fixes (without the self_group change) to cvs now. i hope this is the last fix for this problem...
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Quoted 22 lines · Takashi Iwai
At Wed, 21 May 2003 13:35:39 +0200 (CEST),
Quoted 20 lines · Jaroslav
Quoted 17 lines · Takashi Iwai
At Wed, 21 May 2003 02:32:02 +0200,
Quoted 14 lines · Pieter Palmers
Ok, second try:
alsa 0.9.3c fresh from CVS
---------------------------------------
/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 0.9.3c. Compiled on May 21 2003 for kernel 2.4.20-LL with versioned symbols.
/proc/asound/cards:0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI Ensoniq AudioPCI ENS1371 at 0xb000, irq 5 ---------------------------------------
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
how about this one? this should fix another deadlock (including the simplified expression of stream lock)
Takashi, the
self_groupis designed to avoid mess in the lowlevel drivers.which mess do you mean?
as far as i see, only self_group.lock is used in the code. (so i replacedself_groupwith a single spinlock.)
See: snd_pcm_group_for_each()
If you remove self_group then you must use some condition in lowlevel drivers to distinct standalone and linked streams. I want to avoid this condition.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 14 lines · Pieter Palmers
Quoted 10 lines
ok.
meanwhile, i committed my fixes (without the
self_groupchange) to cvs now. i hope this is the last fix for this problem...So did I, but alas...
installed the new CVS version.
Quoted 9 lines
this time I tried using alsaplayer -d jack.
apart from not getting any sound, all seemed to work for a while. I then Ctrl-C 'd jack and restarted it. Result: instant lockup. I do have the impression that it takes longer for the lockup to occur.
I'll try again with spiralsynthmodular, and I'll try to figure out if the restarting of Jack has something to do with this.
Pieter
and so I tried spiralsynthmodular...
it still hangs the system, but now it runs a little longer than yesterday (a minute instead of some seconds). and the restarting of jack doesn't affect it, i.e. this time it crashed on the first jack session.
I'm sorry that I can't provide you with any more info... if you have some suggestions on gathering more usefull info, please let me know.
Pieter
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Quoted 27 lines · Pieter Palmers
Quoted 11 lines · Pieter Palmers
Quoted 4 lines
ok.
meanwhile, i committed my fixes (without the
self_groupchange) to cvs now. i hope this is the last fix for this problem...So did I, but alas...
installed the new CVS version.
this time I tried using alsaplayer -d jack.
Quoted 8 lines
apart from not getting any sound, all seemed to work for a while. I then Ctrl-C 'd jack and restarted it. Result: instant lockup. I do have the impression that it takes longer for the lockup to occur.
I'll try again with spiralsynthmodular, and I'll try to figure out if the restarting of Jack has something to do with this.
Pieter
and so I tried spiralsynthmodular...
it still hangs the system, but now it runs a little longer than yesterday (a minute instead of some seconds).
and the restarting of jack doesn't affect it, i.e. this time it crashed on the first jack session.
Quoted 4 lines
I'm sorry that I can't provide you with any more info... if you have some suggestions on gathering more usefull info, please let me know.
Pieter
Just a longshot, and forgive me if it's already been raised : you aren't using ext3 by any chance? There are issues with kernel 2.4.20, ext3 which can cause lockups when being used to hard disk recording : this has been shown up while using Ardour. I don't know if it relates, but thought it might help.
t
Signature · 8 lines
GPG: http://n12turbo.com/tarragon/public.key ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Quoted 5 lines
Just a longshot, and forgive me if it's already been raised : you aren't using
ext3 by any chance? There are issues with kernel 2.4.20, ext3 which can cause lockups when being used to hard disk recording : this has been shown up while using Ardour. I don't know if it relates, but thought it might help.
i haven't tried the latest CVS, but the lockups with recent CVS affect me and my system has nothing but ext2.
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge
Quoted 20 lines
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens when jackd xruns. I've been reproducing it using "jackd -d alsa" (other options don't make a difference) then "ladccad". Once the system crashs the only way to get any responce is with SysRq. Keys don't echo to the console and I can't switch VTs.
Generally there is no error message or oops that I can see, even when debug=full is enable in ALSA. Early on I saw a message from jackd to the tune of "error write 512 somethings to device", but I have not been able to reproduce it. I am willing to run any tests that might help. I use journaling filesystems ;-)
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.
SoundBlaster Live! Value
ATI Radeon 8500 (using the closed-source ATI drivers; version 2.9.8)
Quoted 7 lines
My software is:
ALSA drivers 0.9.3a or current CVS
Linux 2.4.20 (vanilla or gentoo patched) Jack 0.71.2
Current Gentoo with testing packages enabled (~x86)
Just want to tell that I'm experiencing almost the same problem (I got a Dual PIII 1Gz 256Mb and two cs46xx soundcards)
After updating ALSA CVS today, jack is no longer able to start, it just locks up my machine, and sometimes even the SysRQ hack dont react. (I've been several hours today fighting with this problem .....) What I was able to find out from the SysRQ is that the EIP all the times seems
to be somewhere at: c0153804 <.text.lock.inode+135/211>, or sync_unlocked_inodes(...) which dont make any sense to me. (?????????????)
One more interesting point is that if I start the jackd without the "-R" flag jack starts for a while, sometimes I'm able to even stop/kill it. But after that no program is able to start or run correctly, which feels like that something is seriously corrupted in the kernel.
Now, for first time in my life I've downgraded ALSA to a previous CVS version, which seems to work with JACK :(
/Benny
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
Quoted 46 lines · Benny Sjostrand
Quoted 20 lines
Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B prints a message saying it will reboot then doesn't). The crash happens when jackd xruns. I've been reproducing it using "jackd -d alsa" (other options don't make a difference) then "ladccad". Once the system crashs the only way to get any responce is with SysRq. Keys don't echo to the console and I can't switch VTs.
Generally there is no error message or oops that I can see, even when debug=full is enable in ALSA. Early on I saw a message from jackd to the tune of "error write 512 somethings to device", but I have not been able to reproduce it. I am willing to run any tests that might help. I use journaling filesystems ;-)
My hardware is:
Dual PIII 1Ghz with 512M RAM on a Tyan MB.
SoundBlaster Live! Value
ATI Radeon 8500 (using the closed-source ATI drivers; version 2.9.8)Quoted 7 lines
My software is:
ALSA drivers 0.9.3a or current CVS
Linux 2.4.20 (vanilla or gentoo patched) Jack 0.71.2
Current Gentoo with testing packages enabled (~x86)Just want to tell that I'm experiencing almost the same problem (I got a Dual PIII 1Gz 256Mb
and two cs46xx soundcards)
After updating ALSA CVS today, jack is no longer able to start, it just locks up my machine, and
sometimes even the SysRQ hack dont react. (I've been several hours today fighting with this problem .....)
What I was able to find out from the SysRQ is that the EIP all the times seems
to be somewhere at:c0153804<.text.lock.inode+135/211>, orsync_unlocked_inodes(...)
which dont make any sense to me. (?????????????)One more interesting point is that if I start the jackd without the "-R" flag jack starts for a while,
sometimes I'm able to even stop/kill it. But after that no program is able to start or run correctly,
which feels like that something is seriously corrupted in the kernel.
Quoted 3 lines
Now, for first time in my life I've downgraded ALSA to a previous CVS version, which seems
to work with JACK :(
It looks like spinlock problem. Could you recompile your kernel and ALSA driver with spinlock debug enabled? Look for DEBUG_SPINLOCKS in linux/include/linux/spinlock.h and change the value 0 to 2.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge