From: "Bjørn Mork" <bjorn@mork.no>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Zdenek Kabelac <zkabelac@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Lan Tianyu <tianyu.lan@intel.com>,
jinchoi@broadcom.com, Paul Bolle <pebolle@tiscali.nl>,
ziegler@email.mathematik.uni-freiburg.de,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
jbarnes@virtuousgeek.org
Subject: Re: Regression with suspend resume 5a87182aa21d6d5d306840feab9321818dd3e2a3
Date: Mon, 16 Dec 2013 12:02:23 +0100 [thread overview]
Message-ID: <87iouprrcw.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAKohpomO+0q7bFWTnFRgqoRuU2WryfPpFv0WLOCKtHBrLzLRqw@mail.gmail.com> (Viresh Kumar's message of "Mon, 16 Dec 2013 16:10:55 +0530")
Viresh Kumar <viresh.kumar@linaro.org> writes:
> On 8 December 2013 15:54, Zdenek Kabelac <zkabelac@redhat.com> wrote:
>> I'm testing recent 3.13-rc kernel - and I've notice my Lenovo T61 is not
>> able to resume. After bisect I've found commit:
>>
>> 5a87182aa21d6d5d306840feab9321818dd3e2a3
>
> That's my patch, sorry for all the trouble.. Just came back after vacations
> and multiple threads are there with this patch as culprit..
>
> I just tested this patch again on Rafael's linux-next branch and suspend/resume
> and Hibernation are working fine for me on my Thinkpad T420. I don't see any
> issues at all..
>
> scaling_governor: ondemand
> scaling_driver: acpi-cpufreq
>
>> When I just revert this commit with 374b105797c3d4f29c685f3be535c35f5689b30e
>> (3.13-rc3) suspend/resume works again.
>> (I'm using ondemand CPU governor)
>
>> Here is bisect log:
>
>> # bad: [2167e2399dc5e69c62db56d933e9c8cbe107620a] cpufreq: fix garbage
>> kobjects on errors during suspend/resume
>> git bisect bad 2167e2399dc5e69c62db56d933e9c8cbe107620a
>
> I don't read bisect logs well but doesn't you log say that the culprit is
> 2167e2399dc5e69c62db56d933e9c8cbe107620a instead?
>
> I am trying with this patch now, but will take some time for results to be out.
It's both patches in combination. Interesting case, really :-)
Bjørn
next prev parent reply other threads:[~2013-12-16 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 10:24 Zdenek Kabelac
2013-12-08 11:13 ` Paul Bolle
2013-12-08 19:21 ` Zdenek Kabelac
2013-12-08 19:33 ` Paul Bolle
2013-12-16 10:40 ` Viresh Kumar
2013-12-16 11:02 ` Bjørn Mork [this message]
2013-12-16 11:28 ` Viresh Kumar
2013-12-16 12:19 ` Bjørn Mork
2013-12-16 13:51 ` Viresh Kumar
2013-12-16 11:36 ` Srivatsa S. Bhat
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=87iouprrcw.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=jbarnes@virtuousgeek.org \
--cc=jinchoi@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tianyu.lan@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=ziegler@email.mathematik.uni-freiburg.de \
--cc=zkabelac@redhat.com \
/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®