From: Stephen Warren <swarren@wwwdotorg.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: cpufreq_stats NULL deref on second system suspend
Date: Tue, 10 Sep 2013 14:53:01 -0600 [thread overview]
Message-ID: <522F86AD.6010603@wwwdotorg.org> (raw)
In-Reply-To: <1775778.MeiRhuYy7o@vostro.rjw.lan>
On 09/09/2013 05:14 PM, Rafael J. Wysocki wrote:
> On Monday, September 09, 2013 03:29:06 PM Stephen Warren wrote:
>> On 09/09/2013 02:24 PM, Rafael J. Wysocki wrote:
>>> On Monday, September 09, 2013 02:01:32 PM Stephen Warren wrote:
>>>> On 09/09/2013 02:01 PM, Rafael J. Wysocki wrote:
>>>>> On Monday, September 09, 2013 01:22:23 PM Stephen Warren wrote:
>>>>>> Viresh,
>>>>>>
>>>>>> I'm seeing the crash below when suspending my system for the second time.
>>>>>>
>>>>>> I can avoid this with the following patch, which adds a check which
>>>>>> already exists in all-but-one other places that the same lookup is made:
>>>>>
>>>>> Which kernel did you test?
>>>>
>>>> next-20130909.
>>>
>>> Is it reproducible with the current mainline?
>>
>> This does not affect v3.11, but does affect current HEAD; 300893b "Merge
>> tag 'xfs-for-linus-v3.12-rc1' of git://oss.sgi.com/xfs/xfs".
>
> What system does it break on?
A dual-core ARM system (NVIDIA Tegra20 SoC, Harmony board).
> Any chance to bisect cpufreq changes between 3.11 and the current HEAD?
Sure, it's due to 5302c3f "cpufreq: Perform light-weight init/teardown
during suspend/resume".
next prev parent reply other threads:[~2013-09-10 20:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 19:22 cpufreq_stats NULL deref on second system suspend Stephen Warren
2013-09-09 20:01 ` Rafael J. Wysocki
2013-09-09 20:01 ` Stephen Warren
2013-09-09 20:24 ` Rafael J. Wysocki
2013-09-09 21:29 ` Stephen Warren
2013-09-09 23:14 ` Rafael J. Wysocki
2013-09-10 20:53 ` Stephen Warren [this message]
2013-09-10 22:34 ` Rafael J. Wysocki
2013-09-11 10:21 ` Srivatsa S. Bhat
2013-09-11 10:44 ` Viresh Kumar
2013-09-11 10:45 ` Viresh Kumar
2013-09-11 11:14 ` Srivatsa S. Bhat
2013-09-11 11:59 ` Viresh Kumar
2013-09-11 13:56 ` Srivatsa S. Bhat
2013-09-12 5:52 ` Viresh Kumar
2013-09-12 6:26 ` Srivatsa S. Bhat
2013-09-12 6:41 ` Viresh Kumar
2013-09-12 6:46 ` Srivatsa S. Bhat
2013-09-12 6:52 ` Viresh Kumar
2013-09-12 7:14 ` Srivatsa S. Bhat
2013-09-12 15:55 ` Stephen Warren
2013-09-12 17:26 ` Srivatsa S. Bhat
2013-09-13 4:26 ` Viresh Kumar
2013-09-11 11:10 ` Srivatsa S. Bhat
2013-09-11 11:15 ` Viresh Kumar
2013-09-11 11:17 ` Srivatsa S. Bhat
2013-09-11 11:41 ` Viresh Kumar
2013-09-11 11:09 ` Srivatsa S. Bhat
2013-09-11 16:05 ` Stephen Warren
2013-09-11 18:03 ` Srivatsa S. Bhat
2013-09-11 18:42 ` Srivatsa S. Bhat
2013-09-11 19:03 ` Stephen Warren
2013-09-11 19:46 ` Srivatsa S. Bhat
2013-09-11 20:07 ` Stephen Warren
2013-09-11 20:05 ` Srivatsa S. Bhat
2013-09-12 6:04 ` Viresh Kumar
2013-09-12 6:00 ` Viresh Kumar
2013-09-12 5:58 ` 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=522F86AD.6010603@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--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).