From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [PATCH v2 12/12] ASoC: SOF: Intel: hda-codec: fix memory allocation Date: Thu, 23 May 2019 10:27:09 +0200 Message-ID: References: <20190522162142.11525-1-pierre-louis.bossart@linux.intel.com> <20190522162142.11525-13-pierre-louis.bossart@linux.intel.com> <96A12704CE18D347B625EE2D4A099D195284169B@SHSMSX103.ccr.corp.intel.com> <96A12704CE18D347B625EE2D4A099D19528416D3@SHSMSX103.ccr.corp.intel.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 mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id CA08FF8079B for ; Thu, 23 May 2019 10:27:10 +0200 (CEST) In-Reply-To: <96A12704CE18D347B625EE2D4A099D19528416D3@SHSMSX103.ccr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" To: "Yang, Libin" Cc: "alsa-devel@alsa-project.org" , "broonie@kernel.org" , Pierre-Louis Bossart List-Id: alsa-devel@alsa-project.org On Thu, 23 May 2019 10:21:20 +0200, Yang, Libin wrote: > > Hi Takashi, > > >-----Original Message----- > >From: Takashi Iwai [mailto:tiwai@suse.de] > >Sent: Thursday, May 23, 2019 4:16 PM > >To: Yang, Libin > >Cc: Pierre-Louis Bossart ; alsa- > >devel@alsa-project.org; broonie@kernel.org > >Subject: Re: [alsa-devel] [PATCH v2 12/12] ASoC: SOF: Intel: hda-codec: fix > >memory allocation > > > >On Thu, 23 May 2019 10:03:03 +0200, > >Yang, Libin wrote: > >> > >> Please let me describe the issue here. > >> > >> The test case is: > >> 1) Unload module with script "sudo ./sof_remove.sh" , > >> 2) reload module with script "sudo ./sof_insert.sh" > >> > >> After several rounds of removing and inserting kernel modules, system > >> will complain like below: > >> "BUG: unable to handle kernel paging request at 000000292a282031" > > > >Did you try some kernel debug options? It might show what went wrong. > > No, I haven't. I'm not sure which options I can use for this case. Could you > please give me some suggestions? You can enable CONFIG_DEBUG_DEVRES and adjust the devres.log option for showing each devres allocation and removal. And I'd try CONFIG_DEBUG_SLAB and CONFIG_DEBUG_KMEMLEAK or whatever interesting in CONFIG_DEBUG section, too. Takashi