public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [Fwd: Commit 555c45fe0d0 ("int340X/processor_thermal_device: add support for MMIO RAPL") boot failure]
Date: Fri, 19 Jul 2019 06:03:57 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1907190601580.2769@hp-x360> (raw)
In-Reply-To: <CAJZ5v0jYdV3esYfj9Yc2NRkdTFNdDvFnuuOe-rTwFQFhFvRH=g@mail.gmail.com>


On Fri, 19 Jul 2019, Rafael J. Wysocki wrote:

> So can you disable PROC_THERMAL_MMIO_RAPL in Kconfig and retest?

It can't be manually disabled, as it's auto-selected:

	Depends on: THERMAL [=y] && (X86 [=y] || X86_INTEL_QUARK [=n] ||
	COMPILE_TEST [=n]) && INT340X_THERMAL [=y] && 64BIT [=y] && POWERCAP [=y]

so I just reverted the commit to get going again,

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Silicon Valley

  reply	other threads:[~2019-07-19 13:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.21.1907181955330.2769@hp-x360>
     [not found] ` <1563514893.2433.3.camel@intel.com>
2019-07-19  6:13   ` [Fwd: Commit 555c45fe0d0 ("int340X/processor_thermal_device: add support for MMIO RAPL") boot failure] Kenneth R. Crudup
2019-07-19  7:51     ` Rafael J. Wysocki
2019-07-19 13:03       ` Kenneth R. Crudup [this message]
2019-07-19 15:34         ` Zhang Rui
2019-07-19 17:31           ` Kenneth R. Crudup
2019-07-20  1:25             ` Zhang Rui
2019-07-20 10:18               ` Rafael J. Wysocki
2019-07-20 12:09                 ` Rafael J. Wysocki
2019-07-19  8:30     ` Rafael J. Wysocki
2019-07-19 11:28       ` Zhang, Rui
2019-07-19 12:33         ` Zhang, Rui
2019-07-19 15:35       ` Zhang Rui
2019-07-20 12:11         ` Rafael J. Wysocki

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=alpine.DEB.2.21.1907190601580.2769@hp-x360 \
    --to=kenny@panix.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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