From: Adrian Bunk <bunk@stusta.de>
To: Daniel Drake <dsd@gentoo.org>, perex@suse.cz
Cc: David Ford <david+challenge-response@blue-labs.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: ALSA bugs with 2.6.12-rc1
Date: Mon, 4 Apr 2005 19:34:53 +0200 [thread overview]
Message-ID: <20050404173453.GB4087@stusta.de> (raw)
In-Reply-To: <4251749B.5060603@gentoo.org>
On Mon, Apr 04, 2005 at 06:08:43PM +0100, Daniel Drake wrote:
> David Ford wrote:
> > It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a
> > null pointer.
> >
> > codec_semaphore: semaphore is not ready [0x1][0x300300]
> > codec_read 0: semaphore is not ready for register 0x2c
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000000
> >
> > This happens on multiple machines, 32b and 64bit. I'll be happy to
> > provide further information if needed.
>
> This only happens when you mismatch your kernel and alsa-lib versions, e.g.
> running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly
> vice-versa.
Are you saying the userspace interface of the ALSA kernel drivers has
incompatible changes between minor versions of ALSA?
If this is true, that's a serious bug.
> Daniel
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-04-04 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 14:46 ALSA bugs with 2.6.12-rc1 David Ford
2005-04-04 17:08 ` Daniel Drake
2005-04-04 17:26 ` Takashi Iwai
2005-04-04 17:34 ` Adrian Bunk [this message]
2005-04-04 18:39 ` Jaroslav Kysela
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=20050404173453.GB4087@stusta.de \
--to=bunk@stusta.de \
--cc=alsa-devel@alsa-project.org \
--cc=david+challenge-response@blue-labs.org \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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