From: Alexander Nyberg <alexn@telia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: Badness in remove_proc_entry called from snd_via82xx_remove (2.6.4-mm)
Date: Thu, 11 Mar 2004 20:44:12 +0100 [thread overview]
Message-ID: <1079034252.428.1.camel@boxen> (raw)
In-Reply-To: <s5hllm7jjc9.wl@alsa2.suse.de>
On Thu, 2004-03-11 at 20:04, Takashi Iwai wrote:
> At Thu, 11 Mar 2004 18:38:16 +0100,
> Alexander Nyberg wrote:
> >
> > This happens at shutdown when alsa is to be closed with kernel 2.6.4-mm.
> > I'm running debian sid, snd_via82xx compiled as module.
> > Happens also on 2.6.4-rc2-mm1, I can try on more kernels as well if it
> > is not a clear case.
> >
> >
> > I slapped a printk on these just before the badness:
> > de->subdir->name = "id", de->name = "card0"
>
> does the attached patch work?
>
>
> --
> Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
> --- linux/sound/core/init.c 4 Mar 2004 17:54:06 -0000 1.37
> +++ linux/sound/core/init.c 11 Mar 2004 19:01:42 -0000
> @@ -281,7 +281,7 @@
> }
> if (card->private_free)
> card->private_free(card);
> - snd_info_free_entry(card->proc_id);
> + snd_info_unregister(card->proc_id);
> if (snd_info_card_free(card) < 0) {
> snd_printk(KERN_WARNING "unable to free card info\n");
> /* Not fatal error */
Yes it worked, no more badness.
Thanks,
Alex
prev parent reply other threads:[~2004-03-11 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:34 2.6.1, Badness in local_bh_enable at kernel/softirq.c:121 Jacek Kawa
2004-03-11 17:38 ` Badness in remove_proc_entry called from snd_via82xx_remove (2.6.4-mm) Alexander Nyberg
2004-03-11 19:04 ` Takashi Iwai
2004-03-11 19:44 ` Alexander Nyberg [this message]
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=1079034252.428.1.camel@boxen \
--to=alexn@telia.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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