From: Takashi Iwai Subject: Re: OOPS: Vmaster not freed on reconfig Date: Tue, 08 Nov 2011 17:36:02 +0100 Message-ID: References: <4EB955F8.5070303@canonical.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 51CD024335 for ; Tue, 8 Nov 2011 17:36:05 +0100 (CET) In-Reply-To: <4EB955F8.5070303@canonical.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: David Henningsson Cc: ALSA Development Mailing List List-Id: alsa-devel@alsa-project.org At Tue, 08 Nov 2011 17:16:56 +0100, David Henningsson wrote: > > Hi, > > I'm playing around with the reconfig functions of snd-hda-codec and got > an OOPS in slave_put. I tried to research this, and I think I've nailed > down the problem: the vmaster is not freed on reconfig (presumably, it > should be fixed in hda_codec.c:snd_hda_ctls_clear). Hmm, I don't figure out how it happens. The vmaster is added to the list via snd_hda_add_vmaster() by calling snd_hda_ctl_add(). > I'm a little unsure of whether the best thing is to just add it to > codec.mixers, keep them in a separate array, or something else. What do > you think? > > (It's on 3.0, it's a sigmatel/IDT, and I've got the screen captured by a > camera if anyone is interested.) Yes, it'd be interesting. If the bug is easily reproducible, you can capture the oops text by netconsole, too. thanks, Takashi