From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Pont <andy.pont@sdcsystems.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Zha Qipeng <qipeng.zha@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: mfd/intel_pmc_bxt: `intel_pmc_get_resources()` results in page fault
Date: Tue, 25 Jan 2022 18:29:19 +0200 [thread overview]
Message-ID: <YfAlXzNKPTWMl/YS@lahna> (raw)
In-Reply-To: <em1f48e0b2-2380-45ef-a0c1-2c38a477aa5f@andys-imac.local>
On Tue, Jan 25, 2022 at 04:27:02PM +0000, Andy Pont wrote:
> Hello Mika,
>
> > Thanks! The dump looks OK to me wrt. the PMC device. However, I think I
> > found the bug.
> >
> > Can you try if the below hack fixes the issue?
> I’ll give the patch a test and let you know how I get on.
>
> Which fields within the ACPI dump are you looking at? When we boot the same
> hardware platform / Ubuntu image with the stock AMI BIOS then we don’t see
> the kernel oops.
Probably the driver is disabled there.
This one:
Device (IPC1)
{
Name (_HID, "INT34D2")
Name (_CID, "INT34D2")
Name (_DDN, "Intel(R) IPC1 Controller")
Name (RBUF, ResourceTemplate ()
{
Memory32Fixed (ReadWrite, 0x0, 0x2000, IBAR)
Memory32Fixed (ReadWrite, 0x0, 0x4, MDAT)
Memory32Fixed (ReadWrite, 0x0, 0x4, MINF)
IO (Decode16, 0x400, 0x480,
0x04, 0x80)
Memory32Fixed (ReadWrite, 0x0, 0x2000, SBAR)
Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive, , , )
{
40
}
})
prev parent reply other threads:[~2022-01-25 16:33 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
[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 [this message]
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=YfAlXzNKPTWMl/YS@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