From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <tfiga@chromium.org>
Cc: "Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Cezary Rojewski" <cezary.rojewski@intel.com>,
"Takashi Iwai" <tiwai@suse.com>,
"Jie Yang" <yang.jie@linux.intel.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
"Liam Girdwood" <liam.r.girdwood@linux.intel.com>,
"Łukasz Majczak" <lmajczak@google.com>,
cujomalainey@chromium.org
Subject: Re: [PATCH] ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function
Date: Wed, 14 Oct 2020 20:02:26 +0100 [thread overview]
Message-ID: <20201014190226.GE4580@sirena.org.uk> (raw)
In-Reply-To: <20201014141624.4143453-1-tfiga@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Wed, Oct 14, 2020 at 02:16:24PM +0000, Tomasz Figa wrote:
> Fixes a boot crash on a HP Chromebook x2:
>
> [ 16.582225] BUG: kernel NULL pointer dereference, address: 0000000000000050
> [ 16.582231] #PF: supervisor read access in kernel mode
> [ 16.582233] #PF: error_code(0x0000) - not-present page
> [ 16.582234] PGD 0 P4D 0
> [ 16.582238] Oops: 0000 [#1] PREEMPT SMP PTI
> [ 16.582241] CPU: 0 PID: 1980 Comm: cras Tainted: G C 5.4.58 #1
> [ 16.582243] Hardware name: HP Soraka/Soraka, BIOS Google_Soraka.10431.75.0 08/30/2018
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-14 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 14:16 [PATCH] ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function Tomasz Figa
2020-10-14 15:30 ` Pierre-Louis Bossart
2020-10-14 19:02 ` Mark Brown [this message]
2020-10-26 22:27 ` Tomasz Figa
2020-10-26 23:10 ` Mark Brown
2020-10-14 19:31 ` Mark Brown
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=20201014190226.GE4580@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=cujomalainey@chromium.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmajczak@google.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=tiwai@suse.com \
--cc=yang.jie@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).