From: Takashi Iwai <tiwai@suse.de>
To: Antti Boman <antti.boman@mindcom.fi>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: snd-cmipci with Jack not working
Date: Thu, 30 Jan 2003 10:44:31 +0100 [thread overview]
Message-ID: <s5hn0ljkm4g.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E386842.5000908@mindcom.fi>
At Thu, 30 Jan 2003 01:48:18 +0200,
Antti Boman wrote:
>
> Thanks, Takashi! I'll get back to these Friday night, as I'm way too
> busy before that. There are some things included below:
>
> Takashi Iwai wrote:
> > at first, please check which chip model you are using and get the
> > register dump from /proc/asound/card0/cmipci.
>
> I thought I sent the chip model to the mailing list, but that was
> actually one of the off-list messages. The model seems to be "C-Media
> PCI CMI8738-MC6 (model 55)", as the dump of /proc/asound/card0/cmipci
> here tells:
ok, then the chip model is the same one as i have now.
> >>I've gathered the key information here:
> >>
> >>- The sound when playing back is totally garbled, the pitch is lower
> >> than the original, and I get lots of clicking alongside. If I'm not
> >> using jack but alsa output, everything (playing and recording) is ok.
> >>
> >>- I have the lowlat patch installed in kernel, but using or not using it
> >> doesn't seem to change anything.
> >
> > most likely the kernel scheduler is irrelevant.
>
> The only effect it had was locking the whole machine when using
> playback/capture only.
do you mean with LL-patch? or with preempt patch?
> >>- Using jackd with playback/capture only, it produces the following
> >> message:
> >> jackd: pcm.c:5851: snd_pcm_mmap_commit: Assertion 'pcm' failed
> >
> > that's weird.
>
> Yes, and as you most probably know, it refers to alsa-lib/src/pcm/pcm.c
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.
> Oh, btw, I'm using alsa 0.9.0rc6, and as root (which you obviously
> already gathered from me using lowlatency patches).
>
> Kernel 2.4.19 with AMD Athlon.
>
> >>- If using kernel real-time patches with playback/capture only, the
> >> system locks up. This doesn't happen with both capture and playback
> >> enabled.
> >
> > i can't produce this on my machine...
>
> Here it does the same thing every time.
ah, sorry, what do you mean "kernel real-time patches"?
preempt-patch?
then i don't know. i don't use them together with 2.4 kernels.
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-30 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 9:27 snd-cmipci with Jack not working Antti Boman
2003-01-29 17:13 ` Takashi Iwai
2003-01-29 23:48 ` Antti Boman
2003-01-30 9:44 ` Takashi Iwai [this message]
2003-01-30 10:00 ` Antti Boman
2003-01-30 10:20 ` Takashi Iwai
2003-01-30 12:29 ` Antti Boman
2003-01-30 10:07 ` Antti Boman
2003-02-12 21:39 ` Antti Boman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hn0ljkm4g.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=antti.boman@mindcom.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox