mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Adam Belay <ambx1@neo.rr.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org
Subject: Re: snd-cs4236 (possibly all isa-pnp cards or all alsa isa-pnp cards) broken in 2.6.16-rc4
Date: Tue, 21 Feb 2006 18:43:50 +0100	[thread overview]
Message-ID: <s5hek1wk3op.wl%tiwai@suse.de> (raw)
In-Reply-To: <43FB3718.6060503@keyaccess.nl>

At Tue, 21 Feb 2006 16:51:52 +0100,
Rene Herman wrote:
> 
> Takashi Iwai wrote:
> 
> > Rene Herman wrote:
> 
> >> I noticed on 2.6.16-rc4 that my MPU-401 wasn't functional, due to a
> >> simple copy & paste error in sound/isa/cs423x/cs4236.c:
> > 
> > Thanks, I applied it to ALSA CVS tree, too.
> 
> The patch Adam sent fixes the ".remove not called" issue. It _also_ 
> fixes the OOPS in snd_timer_free() I sent along, so that one wasn't 
> independent. During testing, I uncovered one more bug though.
> 
> After using aplaymidi (to test cs4236 mpu401), which pulls in 
> snd-seq-oss, modprobe -r snd-cs4236 tells me:
> 
> "ALSA sound/core/device.c:106: device free eee4e000 (from f099153d), not 
> found"
> 
> That then stays until reboot, with a different device address each time.

This is harmless.  The opl3-oss instance was already freed but the
driver tries to release it again just to be sure.

The patch below should fix this annoyance.


Takashi

===

[PATCH] Fix bogus snd_device_free() in opl3-oss.c

Remove snd_device_free() for an opl3-oss instance which should have
been released.

Signed-off-by: Takashi Iwai <tiwai@suse.de>

---
diff -u -r1.14 opl3_oss.c
--- linux/sound/drivers/opl3/opl3_oss.c	17 Nov 2005 14:11:29 -0000	1.14
+++ linux/sound/drivers/opl3/opl3_oss.c	21 Feb 2006 17:38:41 -0000
@@ -146,7 +146,7 @@
 void snd_opl3_free_seq_oss(struct snd_opl3 *opl3)
 {
 	if (opl3->oss_seq_dev) {
-		snd_device_free(opl3->card, opl3->oss_seq_dev);
+		/* The instance should have been released in prior */
 		opl3->oss_seq_dev = NULL;
 	}
 }

  reply	other threads:[~2006-02-21 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 17:18 Rene Herman
2006-02-21  5:27 ` Adam Belay
2006-02-21 15:37   ` Rene Herman
2006-02-21 14:18 ` Takashi Iwai
2006-02-21 15:51   ` Rene Herman
2006-02-21 17:43     ` Takashi Iwai [this message]
2006-02-21 19:35       ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20 16:54 Rene Herman

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=s5hek1wk3op.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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

all inboxes | Powered by JetHome®