[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jKQh-YyjNjCuVqnj_oiPZ+HLLSftd4ECRJ1ZgPiroxSA@mail.gmail.com>
Date: Sun, 4 Feb 2018 10:18:07 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Ville Syrjala <ville.syrjala@...ux.intel.com>
Cc: Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Sudeep Holla <sudeep.holla@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: [PATCH] Revert "cpuidle: Make drivers initialize polling state"
On Sun, Feb 4, 2018 at 10:12 AM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Mon, Jan 22, 2018 at 5:27 PM, Ville Syrjala
> <ville.syrjala@...ux.intel.com> wrote:
>> From: Ville Syrjälä <ville.syrjala@...ux.intel.com>
>>
>> This reverts commit 1b39e3f813b4685c7a30ae964d5529a1b0e3a286.
>>
>> Makes my P3 machine oops somewhere in cpuidle. I suspect
>> CONFIG_ACPI=n may have something to do with this.
>
> And if you don't do CONFIG_ACPI=n, does it still oops?
>
> Anyway, there are later changes depending on this one, so reverting it
> won't work in general.
>
> Let me look deeper at this.
What's there in /sys/devices/system/cpu/cpuidle/current_driver on your
system with the problematic commit reverted?
Powered by blists - more mailing lists