All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: aigilea <i@cpp.in>
Cc: Robert Moore <robert.moore@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: Kernel panic in ACPICA on HP Spectre X360 (Meteor Lake 155H) laptop
Date: Fri, 16 Feb 2024 14:02:11 +0200	[thread overview]
Message-ID: <20240216120211.GR8454@black.fi.intel.com> (raw)
In-Reply-To: <CABYkuAg3rcXT=0-=7EMX8NW3-mU0zYRvp+rOo5nq_7SHdb=cxA@mail.gmail.com>

Hi,

On Fri, Feb 16, 2024 at 10:33:00AM +0300, aigilea wrote:
>    Hello.
>    I've run into a problem with ACPI while trying to run any linux
>    distribution on "HP Spectre x360 14 inch 2-in-1 Laptop PC 14-eu0000" with
>    the latest BIOS "F.05 Rev.A" with kernel versions from 6.5 to 6.7.
>    During the boot or shortly after kernel spits out a crash backtrace
>    originating at "acpi_ps_get_arg" called from "acpi_ps_delete_parse_tree"
>    or at "acpi_ps_delete_parse_tree" itself.
>    It usually results in a panic and the system is halted but in some rare
>    cases it continues to work for some random period of time so I was able to
>    collect some debugging information.
>    I'm attaching parts of the log I've got booting Arch 2024.01 liveusb with
>    kernel 6.6.8 with the following command line:
>    acpi.debug_layer=0x30 acpi.debug_level=0x880640 log_buf_len=256M
>    dyndbg="file device_pm.c +p"
>    Layer is ACPI_PARSER | ACPI_NAMESPACE, level is ACPI_LV_PARSE_TREES |
>    ACPI_LV_EVALUATION | ACPI_LV_NAMES | ACPI_LV_EXEC | ACPI_LV_PARSE
>    I wasn't able to boot more recent kernels to a working state to collect
>    the log but they panic in the very same code.
>    Log part with crash starts at "ACPI: \_SB_.PC00.I2C3: PM: Power state
>    change: D0 -> D3cold" because I think this is what triggers the problem
>    and the crash happens after what looks like a double call of
>    "ps_delete_parse_tree" from "ps_pop_scope" with the same subtree_root arg
>    which should result in use-after-free and a double free.

We have seen similar and I think this should be fixed in the BIOS side
but I'm checking internally if this is the case or what was the
conclusion.

Temporary workaround is to blacklist intel_lpss_pci driver (although you
may lose some of that functionality then but that's still better than
completely non-functional system).

  reply	other threads:[~2024-02-16 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16  7:33 Kernel panic in ACPICA on HP Spectre X360 (Meteor Lake 155H) laptop aigilea
2024-02-16 12:02 ` Mika Westerberg [this message]
2024-02-16 14:36   ` aigilea
2024-02-16 14:46     ` Mika Westerberg
2024-03-01  7:42       ` Mika Westerberg
2024-03-01 14:38         ` aigilea
2024-03-01 17:33           ` Andy Shevchenko

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=20240216120211.GR8454@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=i@cpp.in \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.