All of lore.kernel.org
 help / color / mirror / Atom feed
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 08:55:27 +0300	[thread overview]
Message-ID: <1827037.Yd5d4GH5Ub@spock> (raw)
In-Reply-To: <CAOh2x=k2xpfqz+VjYpPbQy6Z5aeo8DxkYmk7JSmrAZxQOJSU9Q@mail.gmail.com>

On Tuesday 12 August 2014 11:22:28 Viresh Kumar wrote:
> Yeah, because this is happening while the notifiers are being served.
> Can you debug it a bit to go to the exact notifier routine where this
> crashes?

What should I do to debug it? Is that necessary to recompile kernel with full 
debug?

> Which patch are you talking about here?

I thought about this one [1], but I guess that's not my case.

[1] https://lkml.org/lkml/2014/7/16/815

-- 
Oleksandr post-factum Natalenko, MSc
pf-kernel community
https://natalenko.name/

  reply	other threads:[~2014-08-12  5:55 UTC|newest]

Thread overview: 23+ 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 [this message]
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
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-12 23:39                         ` 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=1827037.Yd5d4GH5Ub@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.