From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Meelis Roos <mroos@linux.ee>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
"4 . 14+" <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms
Date: Thu, 07 Dec 2017 13:54:44 +0100 [thread overview]
Message-ID: <7734929.18g54ABnht@aspire.rjw.lan> (raw)
In-Reply-To: <alpine.LRH.2.21.1712071450001.1176@math.ut.ee>
On Thursday, December 7, 2017 1:51:04 PM CET Meelis Roos wrote:
> > On 06-12-17, 20:21, Meelis Roos wrote:
> > > 30000 was not reliable.
> > >
> > > I created root cron job
> > > @reboot sleep 120; /sbin/reboot
> > >
> > > and by the evening it was dead again.
> > >
> > > Will try 50000 tomorrow.
> >
> > Lets make it similar to what it was before my original patch modified
> > it, to avoid all corner cases.
> >
> > Please test against 200 ms, 200000 value here.
>
> I tried
>
> policy->transition_delay_us = 200000;
>
> and it still hangs on top of mainline.
>
> What next?
Well, please try to revert the commit you bisected the problem to and see
if that doesn't hang.
next prev parent reply other threads:[~2017-12-07 12:55 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
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 [this message]
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=7734929.18g54ABnht@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®