From: Meelis Roos <mroos@linux.ee>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.14 regression - hang on shutdown (VIA longhaul related?)
Date: Mon, 27 Nov 2017 22:20:22 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.21.1711272219361.5402@math.ut.ee> (raw)
In-Reply-To: <CAJZ5v0icc0=QgNdCBv65Gwe1svEUfR8eHZ6QGyzX_ArcbBYNMA@mail.gmail.com>
> On Mon, Nov 27, 2017 at 4:19 PM, Meelis Roos <mroos@linux.ee> wrote:
> >> > Please try to replace the 10000 in
> >> > cpufreq_policy_transition_delay_us() with a greater number (say 20000
> >> > or 50000) and see if that helps.
> >>
> >> With 50000 it has worked 4 reboots out of 4.
> >
> > With 20000, it also seems to work 3 out of 3 times.
>
> OK, please test it a bit more just to be sure. If 20000 is
> sufficient, we can easily make this change.
Seems stable, 20+ reboots after diferenet uptimes and workloads were all
successful.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-11-27 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 10:53 4.14 regression - hang on shutdown (VIA longhaul related?) Meelis Roos
2017-11-27 13:26 ` Rafael J. Wysocki
2017-11-27 14:31 ` Meelis Roos
2017-11-27 15:19 ` Meelis Roos
2017-11-27 16:21 ` Rafael J. Wysocki
2017-11-27 20:20 ` Meelis Roos [this message]
2017-11-28 3:11 ` [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms Viresh Kumar
2017-11-28 22:07 ` Rafael J. Wysocki
2017-11-29 6:59 ` Meelis Roos
2017-12-04 15:03 ` Rafael J. Wysocki
2017-12-05 8:18 ` Meelis Roos
2017-12-05 8:54 ` Meelis Roos
2017-12-05 15:26 ` Rafael J. Wysocki
2017-12-06 18:21 ` Meelis Roos
2017-12-07 4:40 ` Viresh Kumar
2017-12-07 5:14 ` Meelis Roos
2017-12-07 7:26 ` Meelis Roos
2017-12-07 9:33 ` Viresh Kumar
2017-12-07 12:51 ` Meelis Roos
2017-12-07 12:54 ` Rafael J. Wysocki
2017-12-07 9:45 ` [PATCH V2] cpufreq: longhaul: Revert transition_delay_us to 200 ms Viresh Kumar
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.LRH.2.21.1711272219361.5402@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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).