From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [BUG] oops in cpufreq driver with AMD Kaveri CPU
Date: Tue, 12 Aug 2014 21:04:30 +0300 [thread overview]
Message-ID: <1449757.YVvGmvgCpE@spock> (raw)
In-Reply-To: <CAOh2x=nJTuKKKyM72MUFSkrsH1eh1YgRUbfLcTCpfZzO85q80w@mail.gmail.com>
Well, I've added the following code to cpufreq_register_notifier()
(drivers/cpufreq/cpufreq.c) to CPUFREQ_TRANSITION_NOTIFIER case:
===
pr_info("Registered transition notifier: %p, (%p)\n", nb->notifier_call, &nb-
>notifier_call);
===
And got the following in my dmesg (only 1 line):
===
$ cat /var/log/kern.log | grep "Registered transition notifier"
Aug 12 17:23:45 defiant kernel: [ 3.084977] cpufreq: Registered transition
notifier: ffffffff81590378, (ffffffff81cb0ba0)
===
System.map tells me, that ffffffff81590378 corresponds to
cpufreq_stat_notifier_trans() (in drivers/cpufreq/cpufreq_stats.c).
Also I've added
===
pr_info("%s\n", __func__);
===
to all callbacks (hello, LXR :)), and got the following occurrences in dmesg:
===
$ cat /var/log/kern.log | egrep -e '(acpi_|cpufreq|notifier)' | awk
'{print($7)}' | sort -u
acpi_processor_ppc_notifier
acpi_thermal_cpufreq_notifier
cpufreq_stat_notifier_policy
===
No extra notifiers are involved so far, but also I haven't caught new hang yet
as it occurs randomly. Still waiting for it, but I hope my little
investigation could help somehow.
On Tuesday 12 August 2014 13:16:25 Viresh Kumar wrote:
> On Tue, Aug 12, 2014 at 12:56 PM, Oleksandr Natalenko
>
> <oleksandr@natalenko.name> wrote:
> > Got that and will try to investigate ASAP.
> >
> > Just to note: I tried to use powersave governor and got the same result. I
> > believe notifiers are used with powersave governor as well. Am I wrong?
> Notifiers are used from the cpufreq core when frequency is changed.
> And the powersave governor should have changed the frequency only
> ONCE, i.e. to go to lowest frequency.
>
> So, it probably happened at the first & only change at that time as well..
> But it shouldn't happen any later. So, see what the log looks like on
> that crash.
--
Oleksandr post-factum Natalenko, MSc
pf-kernel community
https://natalenko.name/
next prev parent reply other threads:[~2014-08-12 18:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 21:39 [BUG] oops in cpufreq driver with AMD Kaveri CPU Oleksandr Natalenko
2014-08-07 20:53 ` Oleksandr Natalenko
2014-08-08 17:26 ` Oleksandr Natalenko
2014-08-12 5:52 ` Viresh Kumar
2014-08-12 5:55 ` Oleksandr Natalenko
2014-08-12 6:16 ` Viresh Kumar
2014-08-12 7:26 ` Oleksandr Natalenko
2014-08-12 7:46 ` Viresh Kumar
2014-08-12 18:04 ` Oleksandr Natalenko [this message]
2014-08-12 18:18 ` Oleksandr Natalenko
2014-08-12 18:54 ` Oleksandr Natalenko
[not found] ` <CAOjmkp_mrMYJJfEqqKtPVrbMuaoJ9W6212LKHETeUsOsJryh-Q@mail.gmail.com>
[not found] ` <CAOjmkp8h19de3bYaLpqmXxEynKi--gHBf6MxXuuNoDzZXw=O8Q@mail.gmail.com>
2014-08-12 23:39 ` Fwd: " Aravind Gopalakrishnan
2014-08-13 8:02 ` Oleksandr Natalenko
2014-08-13 4:36 ` Viresh Kumar
2014-08-13 4:42 ` Viresh Kumar
2014-08-13 5:43 ` Oleksandr Natalenko
2014-11-11 10:41 ` Oleksandr Natalenko
2014-11-18 19:07 ` Oleksandr Natalenko
2015-04-14 16:07 ` Oleksandr Natalenko
2014-08-13 4:32 ` Viresh Kumar
2014-08-13 5:56 ` Oleksandr Natalenko
2014-08-13 12:45 ` Oleksandr Natalenko
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=1449757.YVvGmvgCpE@spock \
--to=oleksandr@natalenko.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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