From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, bp@suse.de, hpa@zytor.com, mingo@redhat.com,
x86@kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
linux-acpi@vger.kernel.org
Cc: pavel@ucw.cz
Subject: ACPI enable on Thinkpad X60 hangs when temperatures are high
Date: Mon, 27 May 2019 12:31:55 +0200 [thread overview]
Message-ID: <20190527103155.GB12391@xo-6d-61-c0.localdomain> (raw)
In-Reply-To: <20190527093938.GA12391@xo-6d-61-c0.localdomain>
Hi!
> > So if you compile a kernel, then reboot, boot will hang after "Freeing SMP
> > alternatives memory" (and then wastes power, making thermal situation even worse).
>
> Normally, next message is "smpboot: CPU0: Genuine Intel...".
>
> I added some printks, and check_bugs() returns. Then it goes to ACPI and never
> comes back...
>
> kernel-parameters.txt points to Documentation/acpi/debug.txt, but that one does not exist.
>
> Any ideas what debugging parameters to use for ACPI? I either get nothing or
> so much that machine does not boot...
I ended up adding printks...
It hangs in acpi_hw_set_mode().
ACPI enable: set mode: acpi
ACPI: hw_set_mode
ACPI: hw_set_mode mode switch
ACPI: write_port?
ACPI: os write port
we write to the port but that never returns.
I assume SMM is doing its magic at that point. Any ideas how to debug it further?
Is it possible that it is some kind of screaming interrupt?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2019-05-27 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190527085155.GA11421@xo-6d-61-c0.localdomain>
2019-05-27 9:39 ` Thinkpad X60 fails to boot while "hot" Pavel Machek
2019-05-27 10:31 ` Pavel Machek [this message]
2019-05-27 10:37 ` ACPI enable on Thinkpad X60 hangs when temperatures are high Pavel Machek
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=20190527103155.GB12391@xo-6d-61-c0.localdomain \
--to=pavel@ucw.cz \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@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).