From: Takashi Iwai <tiwai@suse.de>
To: "Yang, Libin" <libin.yang@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v2 12/12] ASoC: SOF: Intel: hda-codec: fix memory allocation
Date: Thu, 23 May 2019 10:15:54 +0200 [thread overview]
Message-ID: <s5hr28pfux1.wl-tiwai@suse.de> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D195284169B@SHSMSX103.ccr.corp.intel.com>
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.
Takashi
next prev parent reply other threads:[~2019-05-23 8:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 16:21 [PATCH v2 00/12] ASoC: SOF: stability fixes Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 01/12] ASoC: SOF: core: remove DSP after unregistering machine driver Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 02/12] ASoC: SOF: core: remove snd_soc_unregister_component in case of error Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 03/12] ASoC: SOF: core: fix error handling with the probe workqueue Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 04/12] ASoC: SOF: pcm: remove runtime PM calls during pcm open/close Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 05/12] ASoC: SOF: pcm: clear hw_params_upon_resume flag correctly Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 06/12] ASoC: SOF: pcm: remove warning - initialize workqueue on open Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 07/12] ASoC: SOF: control: correct the copy size for bytes kcontrol put Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 08/12] ASoC: SOF: ipc: fix a race, leading to IPC timeouts Pierre-Louis Bossart
2019-05-23 6:34 ` [PATCH v3 " Guennadi Liakhovetski
2019-06-05 11:34 ` Mark Brown
2019-05-22 16:21 ` [PATCH v2 09/12] ASoC: SOF: Intel: hda: fix the hda init chip Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 10/12] ASoC: SOF: Intel: hda: use the defined ppcap functions Pierre-Louis Bossart
2019-06-06 21:27 ` Applied "ASoC: SOF: Intel: hda: use the defined ppcap functions" to the asoc tree Mark Brown
2019-05-22 16:21 ` [PATCH v2 11/12] ALSA: hdac: fix memory release for SST and SOF drivers Pierre-Louis Bossart
2019-05-22 16:21 ` [PATCH v2 12/12] ASoC: SOF: Intel: hda-codec: fix memory allocation Pierre-Louis Bossart
2019-05-23 4:10 ` Yang, Libin
2019-05-23 8:03 ` Yang, Libin
2019-05-23 8:15 ` Takashi Iwai [this message]
2019-05-23 8:21 ` Yang, Libin
2019-05-23 8:27 ` Takashi Iwai
2019-05-23 8:34 ` Yang, Libin
2019-06-03 9:10 ` Yang, Libin
2019-06-03 13:45 ` Pierre-Louis Bossart
2019-06-04 1:38 ` Yang, Libin
2019-06-04 1:21 ` Yang, Libin
2019-06-17 7:30 ` Yang, Libin
2019-05-23 8:24 ` Yang, Libin
2019-05-23 11:35 ` Pierre-Louis Bossart
2019-05-24 1:10 ` Yang, Libin
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=s5hr28pfux1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=libin.yang@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
/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