public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
	NXP Linux Team <Linux-imx@nxp.com>
Subject: Re: cpuidle regression ?
Date: Mon, 9 Dec 2019 12:35:19 +0100	[thread overview]
Message-ID: <a2f4c5f4-e416-93dd-24f9-431308a692a0@linaro.org> (raw)
In-Reply-To: <CAJZ5v0i44Rb8PeB65sZmnu=8Ctzjw4BeSHqQC2XTG5A7K2pcsw@mail.gmail.com>

On 09/12/2019 11:50, Rafael J. Wysocki wrote:
> On Mon, Dec 9, 2019 at 11:32 AM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> On 09/12/2019 10:26, Rafael J. Wysocki wrote:
>>> On Sun, Dec 8, 2019 at 11:40 AM Daniel Lezcano
>>> <daniel.lezcano@linaro.org> wrote:
>>>>
>>>>
>>>> Hi Rafael,
>>>>
>>>> the latest linux-next kernelci report indicates a kernel bug for the
>>>> imx6 platform. I don't have this board so it is not possible to
>>>> investigate it.
>>>>
>>>> https://storage.kernelci.org/next/master/next-20191208/arm/multi_v7_defconfig/gcc-8/lab-collabora/boot-imx6q-sabrelite.html
>>>>
>>>> [ ... ]
>>>>
>>>> [    3.372501] Unable to handle kernel NULL pointer dereference at
>>>> virtual address 00000000
>>>>
>>>> [ ... ]
>>>>
>>>> [    3.408898] PC is at _find_first_bit_le+0xc/0x2c
>>>> [    3.413785] LR is at cpuidle_driver_state_disabled+0x40/0xa0
>>>>
>>>>
>>>> Not sure if it is related to the latest changes or not.
>>>
>>> It does seem so, in which case the attached patch should address it.
>>>
>>> Is there a way to test the patch alone or do I need to push it
>>> somewhere to be tested?
>>
>> Is the bleeding-edge branch monitored by kernelci ?
> 
> No, it is not right now, AFAICS.

I have a imx7, I will try to reproduce the issue on it. Otherwise, I can
test on the 'testing' thermal branch temporarily.



-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2019-12-09 11:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 10:39 cpuidle regression ? Daniel Lezcano
2019-12-09  9:26 ` Rafael J. Wysocki
2019-12-09 10:32   ` Daniel Lezcano
2019-12-09 10:50     ` Rafael J. Wysocki
2019-12-09 11:35       ` Daniel Lezcano [this message]
2019-12-09 11:55         ` Rafael J. Wysocki
2019-12-09 17:22           ` Daniel Lezcano
2019-12-10  8:06             ` Daniel Lezcano
2019-12-10  8:07               ` Rafael J. Wysocki
2019-12-10 11:48 ` [PATCH] cpuidle: Fix cpuidle_driver_state_disabled() 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=a2f4c5f4-e416-93dd-24f9-431308a692a0@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Linux-imx@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@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