From: Jan Engelhardt <jengelh@inai.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: Linux hangs at ACPI init on Medion P15648 MD63490
Date: Mon, 17 Feb 2020 01:10:45 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2002170109040.8537@n3.vanv.qr> (raw)
In-Reply-To: <CAJZ5v0jOOi0SjZ+SUv8L8f6z2uxu40Q7AP_q9XKVEOePxwBHfg@mail.gmail.com>
On Sunday 2020-02-16 21:49, Rafael J. Wysocki wrote:
>> I thus went back to 5.6-rc and enabled full ACPI tracing
>> (layer=0xffffffff/level=0xffffffff) starting from
>>
>> nsinit.c:213 /* Walk namespace to execute all _INIs on present devices */
>>
>> onwards. That log output is at http://inai.de/files/m923.mp4 [53MB].
>
>If that is the case, then AFAICS the issue may not be directly related
>to the EC at all. This output only means that the system has an ECDT,
>but that should not be a problem by itself.
>
>The system appears to hang somewhere in acpi_ns_initialize_devices()
>and it is hard to say where exactly.
I had an exact stack trace. (Stashed in all those videos - now extracted and
posted to the bug)
>I would suggest creating a BZ entry at bugzilla.kernel.org for this
>issue and attaching the output of acpidump from the affected system in
>there.
https://bugzilla.kernel.org/show_bug.cgi?id=206553
next prev parent reply other threads:[~2020-02-17 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 19:28 Linux hangs at ACPI init on Medion P15648 MD63490 Jan Engelhardt
2020-02-16 0:32 ` Rafael J. Wysocki
2020-02-16 14:15 ` Jan Engelhardt
2020-02-16 20:49 ` Rafael J. Wysocki
2020-02-17 0:10 ` Jan Engelhardt [this message]
2020-02-17 20:23 ` Rafael J. Wysocki
2020-02-25 15:09 ` Moore, Robert
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=nycvar.YFH.7.76.2002170109040.8537@n3.vanv.qr \
--to=jengelh@inai.de \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
/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).