All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
Date: Wed, 11 Jun 2014 17:50:57 +0000	[thread overview]
Message-ID: <bug-77201-12968-N91YYlQEzL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77201-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=77201

--- Comment #48 from Srivatsa S. Bhat <srivatsa@mit.edu> ---

Hmm, this just became even more hard :-(

Viresh, sure, I'll check the diff tomorrow to see if there is any obvious
breakage.

Meanwhile, can the bug reporter please test these commits that I mentioned
earlier? (6f1e4efd882 is my first suspect commit after 3.13.8)

6f1e4efd882 (cpufreq: Fix timer/workqueue corruption by protecting reading
governor_enabled)

1c0ca90207 (cpufreq: don't call cpufreq_update_policy() on CPU addition)

4e97b631f24 (cpufreq: Initialize governor for a new policy under policy->rwsem)

I know that the issue might not be in cpufreq (especially after your test
results from Viresh's branch). But I still I have some tiny hope that we might
have missed something in cpufreq... Besides, bisecting within the cpufreq
commits is a lot faster than bisecting everything between 3.13.8 and 3.14, in
case the bug is really in cpufreq.

By the way, testing the above commits means that you need to test 1 commit
before the commits mentioned above and see if it works, and then go to the
mentioned commit and see if it fails.

Regards,
Srivatsa S. Bhat

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-06-11 17:50 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-77201-12968@https.bugzilla.kernel.org/>
2014-06-09 20:38 ` [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded bugzilla-daemon
2014-06-09 21:58 ` bugzilla-daemon
2014-06-09 22:01 ` bugzilla-daemon
2014-06-09 23:15 ` bugzilla-daemon
2014-06-10  4:41 ` bugzilla-daemon
2014-06-10  5:26 ` bugzilla-daemon
2014-06-10 12:44 ` bugzilla-daemon
2014-06-10 12:44 ` bugzilla-daemon
2014-06-10 12:45 ` bugzilla-daemon
2014-06-10 12:45 ` bugzilla-daemon
2014-06-10 12:46 ` bugzilla-daemon
2014-06-10 14:06 ` bugzilla-daemon
2014-06-10 14:42 ` bugzilla-daemon
2014-06-10 14:43 ` bugzilla-daemon
2014-06-10 14:47 ` bugzilla-daemon
2014-06-10 15:35 ` bugzilla-daemon
2014-06-10 16:47 ` bugzilla-daemon
2014-06-10 16:48 ` bugzilla-daemon
2014-06-10 19:04 ` bugzilla-daemon
2014-06-10 19:53 ` bugzilla-daemon
2014-06-11 10:28 ` bugzilla-daemon
2014-06-11 10:29 ` bugzilla-daemon
2014-06-11 11:01 ` bugzilla-daemon
2014-06-11 11:04 ` bugzilla-daemon
2014-06-11 11:12 ` bugzilla-daemon
2014-06-11 11:18 ` bugzilla-daemon
2014-06-11 11:37 ` bugzilla-daemon
2014-06-11 12:02 ` bugzilla-daemon
2014-06-11 12:06 ` bugzilla-daemon
2014-06-11 13:50 ` bugzilla-daemon
2014-06-11 13:51 ` bugzilla-daemon
2014-06-11 13:55 ` bugzilla-daemon
2014-06-11 14:10 ` bugzilla-daemon
2014-06-11 14:21 ` bugzilla-daemon
2014-06-11 14:42 ` bugzilla-daemon
2014-06-11 15:35 ` bugzilla-daemon
2014-06-11 15:59 ` bugzilla-daemon
2014-06-11 17:50 ` bugzilla-daemon [this message]
2014-06-11 18:40 ` bugzilla-daemon
2014-06-11 19:35 ` bugzilla-daemon
2014-06-11 19:42 ` bugzilla-daemon
2014-06-11 19:43 ` bugzilla-daemon
2014-06-12  2:36 ` bugzilla-daemon
2014-06-12  2:48 ` bugzilla-daemon
2014-06-12  2:49 ` bugzilla-daemon
2014-06-12  9:48 ` bugzilla-daemon
2014-06-12 10:18 ` bugzilla-daemon
2014-06-12 13:22 ` bugzilla-daemon
2014-06-12 14:20 ` bugzilla-daemon
2014-06-12 14:30 ` bugzilla-daemon
2014-06-12 14:31 ` bugzilla-daemon
2014-06-12 14:34 ` bugzilla-daemon
2014-06-12 15:14 ` bugzilla-daemon
2014-06-12 15:29 ` bugzilla-daemon
2014-06-12 16:26 ` bugzilla-daemon
2014-06-12 16:48 ` bugzilla-daemon
2014-06-12 19:27 ` bugzilla-daemon
2014-06-12 21:28 ` bugzilla-daemon
2014-06-12 23:41 ` bugzilla-daemon
2014-06-13  4:14 ` bugzilla-daemon
2014-06-13  4:20 ` bugzilla-daemon
2014-06-13  5:18 ` bugzilla-daemon
2014-06-13 10:49 ` bugzilla-daemon
2014-06-13 21:23 ` bugzilla-daemon
2014-06-14 20:05 ` bugzilla-daemon
2014-06-14 20:08 ` bugzilla-daemon
2014-06-14 20:09 ` bugzilla-daemon
2014-06-14 20:11 ` bugzilla-daemon
2014-06-14 20:13 ` bugzilla-daemon
2014-06-14 20:20 ` bugzilla-daemon
2014-06-15  5:00 ` bugzilla-daemon
2014-06-15 10:30 ` bugzilla-daemon
2014-06-15 10:31 ` bugzilla-daemon
2014-06-15 10:32 ` bugzilla-daemon
2014-06-15 23:13 ` bugzilla-daemon
2014-06-16  5:43 ` bugzilla-daemon
2014-06-16  9:36 ` bugzilla-daemon
2014-06-16  9:36 ` bugzilla-daemon
2014-06-16  9:51 ` bugzilla-daemon
2014-06-16 12:11 ` bugzilla-daemon
2014-06-16 12:47 ` bugzilla-daemon
2014-06-16 12:51 ` bugzilla-daemon
2014-06-16 13:15 ` bugzilla-daemon
2014-06-16 13:27 ` bugzilla-daemon
2014-06-16 15:31 ` bugzilla-daemon
2014-06-16 15:41 ` bugzilla-daemon
2014-06-16 23:22 ` bugzilla-daemon

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=bug-77201-12968-N91YYlQEzL@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.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.