From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Zha Qipeng <qipeng.zha@intel.com>,
linux-kernel@vger.kernel.org,
Andy Pont <andy.pont@sdcsystems.com>
Subject: Re: mfd/intel_pmc_bxt: `intel_pmc_get_resources()` results in page fault
Date: Tue, 25 Jan 2022 16:53:05 +0200 [thread overview]
Message-ID: <YfAO0SPAK7r4zvUE@lahna> (raw)
In-Reply-To: <2ebf7968-a324-6f98-e178-45d4d19cfb48@molgen.mpg.de>
On Tue, Jan 25, 2022 at 03:40:54PM +0100, Paul Menzel wrote:
> [Cc: +Andy]
>
> Dear Mika,
>
>
> Am 25.01.22 um 15:26 schrieb Mika Westerberg:
>
> > On Tue, Jan 25, 2022 at 02:08:53PM +0100, Paul Menzel wrote:
>
> > > `intel_pmc_get_resources()` does not set the name member in the `resource`
> > > struct `gcr_res` resulting in a page fault.
> >
> > On which system you reproduce this,
>
> The dump contains the name:
>
> Hardware name: Star Labs Lite/Lite, BIOS 8 01/24/2022
>
> > and how? Can you also share ACPI dump from that system.
>
> Note, I only forwarded this from a report in #coreboot. The reporter Andy is
> now in Cc.
>
> Unrelated from that information, the Linux kernel should never run into a
> page fault and not trust system data.
Right but this looks like an issue with the system ACPI tables so at
least we should report this to the vendor too so they can fix it in
future revisions.
next prev parent reply other threads:[~2022-01-25 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 13:08 mfd/intel_pmc_bxt: `intel_pmc_get_resources()` results in page fault Paul Menzel
2022-01-25 14:26 ` Mika Westerberg
2022-01-25 14:40 ` Paul Menzel
2022-01-25 14:53 ` Mika Westerberg [this message]
[not found] ` <em755e7a07-2a6b-4b3a-9bc8-5f28857392dc@andys-imac.local>
2022-01-25 15:45 ` Mika Westerberg
2022-01-25 16:27 ` Andy Pont
2022-01-25 16:29 ` Mika Westerberg
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=YfAO0SPAK7r4zvUE@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=andy.pont@sdcsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=qipeng.zha@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