From: Jeremy Linton <jeremy.linton@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: erik.schmauss@intel.com,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: 4.18rc3 TX2 boot failure with "ACPICA: AML parser: attempt to continue loading table after error"
Date: Mon, 9 Jul 2018 15:45:00 -0500 [thread overview]
Message-ID: <f89404f9-fd54-cc2b-4fbe-f1feba4e5364@arm.com> (raw)
In-Reply-To: <6074707.jx9F3QFrWC@aspire.rjw.lan>
Hi,
First thanks for the patch..
On 07/08/2018 04:14 AM, Rafael J. Wysocki wrote:
> On Monday, July 2, 2018 11:41:42 PM CEST Jeremy Linton wrote:
>> Hi,
>>
>> I'm experiencing two problems with commit 5088814a6e931 which is
>> "ACPICA: AML parser: attempt to continue loading table after error"
>>
>> The first is this boot failure on a thunderX2:
>>
>> [ 10.770098] ACPI Error: Ignore error and continue table load
[trimming]
>> ]---
>>
>> Which does appear to be the result of some bad data in the table, but it
>> was working with 4.17, and reverting this commit solves the problem.
>
> Does the patch below make any difference?
>
> ---
> drivers/acpi/acpica/psobject.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Index: linux-pm/drivers/acpi/acpica/psobject.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/acpica/psobject.c
> +++ linux-pm/drivers/acpi/acpica/psobject.c
> @@ -39,6 +39,9 @@ static acpi_status acpi_ps_get_aml_opcod
> ACPI_FUNCTION_TRACE_PTR(ps_get_aml_opcode, walk_state);
>
> walk_state->aml = walk_state->parser_state.aml;
> + if (!walk_state->aml)
> + return AE_CTRL_PARSE_CONTINUE;
> +
Well this seems to avoid the crash, but now it hangs right after on the
"Ignore error and continue table load" message. I would post the DSDT
but I'm borrowing this machine, and I understand the firmware to be an
early release, so...
Anyway, now that I have access again, i'm turning up the debug
messaging, let me see if that points at whats causing the hang.
Thanks,
next prev parent reply other threads:[~2018-07-09 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:41 Jeremy Linton
2018-07-02 21:52 ` Rafael J. Wysocki
2018-07-02 22:30 ` Jeremy Linton
2018-07-03 7:51 ` Rafael J. Wysocki
2018-07-03 20:31 ` Schmauss, Erik
2018-07-08 9:14 ` Rafael J. Wysocki
2018-07-09 20:45 ` Jeremy Linton [this message]
2018-07-09 21:28 ` Rafael J. Wysocki
2018-07-10 3:44 ` Jeremy Linton
2018-07-10 11:13 ` Rafael J. Wysocki
2018-07-10 11:25 ` Rafael J. Wysocki
2018-07-10 15:04 ` Jeremy Linton
2018-07-10 16:56 ` Rafael J. Wysocki
2018-07-10 17:04 ` Jeremy Linton
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=f89404f9-fd54-cc2b-4fbe-f1feba4e5364@arm.com \
--to=jeremy.linton@arm.com \
--cc=erik.schmauss@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
/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
Powered by JetHome