public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>,
	<sedat.dilek@gmail.com>, "'Thomas Gleixner'" <tglx@linutronix.de>
Cc: "'Jani Nikula'" <jani.nikula@intel.com>,
	"'Pavel Machek'" <pavel@ucw.cz>,
	"'Rafael J. Wysocki'" <rafael.j.wysocki@intel.com>,
	"'Daniel Vetter'" <daniel.vetter@ffwll.ch>,
	"'Chris Wilson'" <chris@chris-wilson.co.uk>,
	"'intel-gfx'" <intel-gfx@lists.freedesktop.org>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	"'the arch/x86 maintainers'" <x86@kernel.org>,
	"'Mika Kuoppala'" <mika.kuoppala@linux.intel.com>,
	"'Linux PM'" <linux-pm@vger.kernel.org>
Subject: RE: [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?)
Date: Wed, 28 Dec 2016 16:28:21 -0800	[thread overview]
Message-ID: <001d01d2616a$78fefc50$6afcf4f0$@net> (raw)
In-Reply-To: MMlxcy4WIL5mtMMlycGjUh

On 2016.12.28 14:33 Rafael J. Wysocki wrote:
> On Wed, Dec 28, 2016 at 11:00 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> On Wed, Dec 28, 2016 at 9:29 AM, Jani Nikula <jani.nikula@intel.com> wrote:
>>> On Wed, 28 Dec 2016, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>>> On Tue, Dec 27, 2016 at 10:13 PM, Pavel Machek <pavel@ucw.cz> wrote:
>>>>
>>>> P.S.: Revert "cpu/hotplug: Prevent overwriting of callbacks"
>>>>
>>>> This reverts commit dc280d93623927570da279e99393879dbbab39e7
>>>> Author: Thomas Gleixner <tglx@linutronix.de>
>>>> Date: Wed Dec 21 20:19:49 2016 +0100
>>>> cpu/hotplug: Prevent overwriting of callbacks

With respect to kernel 4.10-rc1 and the above referenced commit:

On my computer rdmsr was not working, and therefore many tools
that use it (i.e. turbostat) were also broken.

I bisected the kernel down to the same above referenced commit.
After finding some potentially related e-mails, I built a
4.10-rc1+ kernel with these:

0dad3a3 x86/mce/AMD: Make the init code more robust
b9d9d69 smp/hotplug: Undo tglxs brainfart
b4b8664 arm64: don't pull uaccess.h into *.S
7ce7d89 Linux 4.10-rc1

And now rdmsr is working fine, as is trubostat.

  parent reply	other threads:[~2016-12-29  0:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 23:09 [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?) Sedat Dilek
2016-12-27  7:42 ` Sedat Dilek
2016-12-27 10:24 ` Chris Wilson
2016-12-27 15:10   ` Daniel Vetter
2016-12-27 15:55     ` Sedat Dilek
2016-12-27 16:07       ` Sedat Dilek
2016-12-28  9:04         ` [Intel-gfx] " Saarinen, Jani
2016-12-27 21:13 ` Pavel Machek
2016-12-28  8:07   ` Sedat Dilek
2016-12-28  8:29     ` Jani Nikula
2016-12-28 10:00       ` Sedat Dilek
2016-12-28 11:00         ` Sedat Dilek
2016-12-28 22:32         ` Rafael J. Wysocki
2016-12-29  0:43           ` Sedat Dilek
2016-12-29  9:50             ` Jani Nikula
2016-12-29 11:58             ` Mika Kuoppala
2016-12-30 11:19               ` Sedat Dilek
2016-12-29  0:28         ` Doug Smythies [this message]
2016-12-29  7:28     ` Sedat Dilek

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='001d01d2616a$78fefc50$6afcf4f0$@net' \
    --to=dsmythies@telus.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mika.kuoppala@linux.intel.com \
    --cc=pavel@ucw.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox