From: Dave Hansen <dave@sr71.net>
To: LKML <linux-kernel@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
John Stultz <john.stultz@linaro.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: hangs in verify_pmtmr_rate()
Date: Wed, 03 Jun 2015 12:55:27 -0700 [thread overview]
Message-ID: <556F5BAF.8010303@sr71.net> (raw)
I'm seeing boot hangs when trying to boot a 32-bit 4.1.0-rc5 kernel on
some 64-bit CPUs (I'm not sure if it is a regression). The NMI watchdog
shows init_acpi_pm_clocksource() as the last thing in the backtrace,
specifically verify_pmtmr_rate()'s I/O instructions. It appears to be
mach_countup()'s while loop that gets stuck.
Booting with "pmtmr=0" works around this for me, as would unsetting
CONFIG_X86_PM_TIMER I'd imagine.
The hardware I'm doing this on is a bit wonky and I think the hpet is
broken on it.
Does this look like *really* broken hardware, or something that we
should be detecting and able to recover from?
next reply other threads:[~2015-06-03 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 19:55 Dave Hansen [this message]
2015-06-03 20:46 ` hangs in verify_pmtmr_rate() John Stultz
2015-06-03 21:11 ` Dave Hansen
2015-06-03 21:48 ` Yu, Fenghua
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=556F5BAF.8010303@sr71.net \
--to=dave@sr71.net \
--cc=fenghua.yu@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.