From: Thomas Gleixner <tglx@linutronix.de>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Martin Peres <martin.peres@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Marc Zyngier <marc.zyngier@arm.com>,
jeffy.chen@rock-chips.com
Subject: Re: [PATCH] x86/hpet: Cure interface abuse in the resume path
Date: Tue, 1 Aug 2017 12:59:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708011254460.1919@nanos> (raw)
In-Reply-To: <58295cdc-0227-8a85-1b27-e56d8b3afd06@intel.com>
On Tue, 1 Aug 2017, Tomi Sarvela wrote:
> On 01/08/17 10:43, Thomas Gleixner wrote:
> > Tomi, can you please do me a favor?
> >
> > Use plain 4.13-rc3 (without that patch) and add the following on the kernel
> > command line: 'nohpet'. Boot the machine and capture and provide the output
> > of
> >
> > # dmesg
> > # cat /proc/interrupts
> > # cat /proc/timer_list
> >
> > Then try the suspend cycle again.
>
> Trying with Linus' tree, tag v4.13-rc3 with nohpet on cmdline.
>
> Outputs below. The nohpet option works, as suspend-resumes complete.
So why didn't this work the first time I asked for that?
http://lkml.kernel.org/r/ddc71535-02de-5b42-934f-70bc5ad43bb7@intel.com
Sigh, that would have spared a lot of pointlessly wasted time....
Thanks,
tglx
next prev parent reply other threads:[~2017-08-01 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 20:07 [PATCH] x86/hpet: Cure interface abuse in the resume path Thomas Gleixner
2017-07-31 22:22 ` Rafael J. Wysocki
2017-08-01 7:30 ` Tomi Sarvela
2017-08-01 7:43 ` Thomas Gleixner
2017-08-01 8:21 ` Tomi Sarvela
2017-08-01 10:59 ` Thomas Gleixner [this message]
2017-08-01 11:07 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
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=alpine.DEB.2.20.1708011254460.1919@nanos \
--to=tglx@linutronix.de \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=martin.peres@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tomi.p.sarvela@intel.com \
--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).