From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Marcin Ślusarz" <marcin.slusarz@gmail.com>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: Crash in acpi_ns_validate_handle triggered by soundwire on Linux 5.10
Date: Wed, 27 Jan 2021 11:28:25 -0600 [thread overview]
Message-ID: <1dc2639a-ecbc-c554-eaf6-930256dcda96@linux.intel.com> (raw)
In-Reply-To: <CA+GA0_sCdowanpZmg==c+xVqqNxG5whLGsKHaCfSmpERBhqMzA@mail.gmail.com>
> Weird, I can't reproduce this problem with my self-compiled kernel :/
> I don't even see soundwire modules loaded in. Manually loading them of course
> doesn't do much.
>
> Previously I could boot into the "faulty" kernel by using "recovery mode", but
> I can't do that anymore - it crashes too.
>
> Maybe there's some kind of race and this bug depends on some specific
> ordering of events?
missing Kconfig?
You need CONFIG_SOUNDWIRE and CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE
selected to enter this sdw_intel_acpi_scan() routine.
next prev parent reply other threads:[~2021-01-27 17:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 19:56 Crash in acpi_ns_validate_handle triggered by soundwire on Linux 5.10 Marcin Ślusarz
2021-01-20 20:34 ` Rafael J. Wysocki
2021-01-20 22:28 ` Pierre-Louis Bossart
2021-01-21 17:47 ` Marcin Ślusarz
2021-01-27 16:36 ` Marcin Ślusarz
2021-01-27 17:28 ` Pierre-Louis Bossart [this message]
2021-01-27 19:18 ` Marcin Ślusarz
2021-01-27 21:52 ` Pierre-Louis Bossart
2021-01-27 22:02 ` Pierre-Louis Bossart
2021-01-28 13:25 ` Marcin Ślusarz
2021-01-28 13:31 ` Rafael J. Wysocki
2021-01-28 12:13 ` Rafael J. Wysocki
2021-01-28 12:39 ` Rafael J. Wysocki
2021-01-28 13:45 ` Marcin Ślusarz
2021-01-28 14:32 ` Marcin Ślusarz
2021-01-29 18:59 ` Marcin Ślusarz
2021-01-29 20:03 ` Marcin Ślusarz
2021-02-01 11:42 ` Rafael J. Wysocki
2021-02-01 12:16 ` Marcin Ślusarz
2021-02-04 12:11 ` Marcin Ślusarz
2021-02-04 12:48 ` Marcin Ślusarz
2021-02-05 15:40 ` [PATCH] soundwire: intel: fix possible crash when no device is detected (was Re: Crash in acpi_ns_validate_handle triggered by soundwire on Linux 5.10) Marcin Ślusarz
2021-02-05 16:16 ` Pierre-Louis Bossart
2021-02-08 12:01 ` [PATCH 1/2] soundwire: intel: fix possible crash when no device is detected Marcin Ślusarz
2021-02-08 12:01 ` [PATCH 2/2] ACPICA: update documentation of acpi_walk_namespace Marcin Ślusarz
2021-02-08 12:43 ` Rafael J. Wysocki
2021-02-08 12:37 ` [PATCH 1/2] soundwire: intel: fix possible crash when no device is detected Rafael J. Wysocki
2021-02-10 23:15 ` Pierre-Louis Bossart
2021-02-11 5:20 ` Vinod Koul
2021-01-28 13:29 ` Crash in acpi_ns_validate_handle triggered by soundwire on Linux 5.10 Marcin Ślusarz
2021-01-28 13:36 ` Rafael J. Wysocki
2021-01-25 18:38 ` Salvatore Bonaccorso
2021-01-25 19:26 ` Pierre-Louis Bossart
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=1dc2639a-ecbc-c554-eaf6-930256dcda96@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@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;
as well as URLs for NNTP newsgroup(s).