Takashi Iwai wrote:
At Thu, 30 Jan 2003 12:00:32 +0200, Antti Boman wrote:
>>
Well, I've gone along with the recommendations of LAU Low-latency Howto at http://www.djcj.org/LAU/guide/Low_latency-Mini-HOWTO.php3 but then again, the basic problem I'm experiencing is not that enabling LL crashes the machine. It's the fact that I cannot get anything but garbled audio out of jackd with cmipci, along with the symptoms of playback/capture only.Andrew Morton's (http://www.zip.com.au/~akpm/linux/schedlat.html#downloads) patch. Sorry about the flaws in terminology, I'm kind of half-dumb with these. If there are even difference with those ones, I have to check them out tonight and tell you then.basically LL-patch is safer...
But yes, I will get into those safety issues when I get the basics working :)
anyway i recommed to use without LL-patch (or disabled via sysctl) as the first tests.
"echo 0 > /proc/sys/kernel/lowlatency" is enough, right?
Yes, I found that out, too. I just wanted to do the tests with both LL enabled and disabled, and obviously ran more tests with it enabled, as it caused more severe errors :)otherwise we don't know which is the culprit. as long as no heavy disk access, the normal scheduler should work fine.
Ok, that's what I'll do tonight or tomorrow. I'll have all the weekend for solving this problem, and I will try to solve it even if it takes the whole weekend.you can run non-stripped jackd in the source tree before installation,I know. But I don't know if it's directly called from jackd. I'll try and ask more on jackit-devel or try to find things myself. May be another dead-end, though.if the above function is directly called from jack, then it should be a bug of jack. the error above says the passed argument is a null pointer.
and run from gdb to trace at which point this happens.
Ok. The second one definitely crashes every time.Then again, even without enabling low latency (whatsoever) it doesn't work. I'm just afraid this won't be solved. And I'm not afraid for myself, just for the fact that 8738 is a highly used chip. Have you tried running jackd with the one of yours?
yes. no hang up with -R and/or -P options, so far. # jackd -v -R -d alsa -d hw -r 44100 -p 512 -n 2 # jackd -v -R -d alsa -d hw -r 44100 -p 512 -n 2 -P
Did you see the message in the the original thread in jackit-devel concerning watching /proc/asound/card0/pcm0p/sub0/status and /proc/asound/card0/pcm0c/sub0/status? If you did, was there anything abnormal there? If not, here's a link in case you want to see the results:
http://sourceforge.net/mailarchive/message.php?msg_id=3656330
Thanks a lot, Takashi, for helping me out. I'll do the tests and debugging you asked me to do as soon as I find the time for it. Tomorrow night if not before that.
-a
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
