From: Rong Chen <rong.a.chen@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
kernel test robot <lkp@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
LKP <lkp@lists.01.org>
Subject: Re: [LKP] Re: de8f5e4f2d ("lockdep: Introduce wait-type checks"): [ 17.344674] EIP: default_idle
Date: Fri, 3 Apr 2020 14:52:58 +0800 [thread overview]
Message-ID: <75dd6e6b-745d-23be-6d3d-1984b1f7f47d@intel.com> (raw)
In-Reply-To: <87h7y2ns2j.fsf@nanos.tec.linutronix.de>
On 4/2/20 5:40 PM, Thomas Gleixner wrote:
> kernel test robot <lkp@intel.com> writes:
>> Greetings,
>>
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>
>> commit de8f5e4f2dc1f032b46afda0a78cab5456974f89
>> Author: Peter Zijlstra <peterz@infradead.org>
>> AuthorDate: Sat Mar 21 12:26:01 2020 +0100
>> Commit: Peter Zijlstra <peterz@infradead.org>
>> CommitDate: Sat Mar 21 16:00:24 2020 +0100
>>
>> lockdep: Introduce wait-type checks
> Can you please avoid enabling
>
>> CONFIG_PROVE_RAW_LOCK_NESTING=y
> for now?
>
> As the changelog states, there are known issues and that's why the
> config is default=n.
Hi Thomas,
Thanks for the advice, we have disabled CONFIG_PROVE_RAW_LOCK_NESTING.
Best Regards,
Rong Chen
prev parent reply other threads:[~2020-04-03 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:17 kernel test robot
2020-04-02 9:40 ` Thomas Gleixner
2020-04-02 9:58 ` Sebastian Andrzej Siewior
2020-04-03 6:52 ` Rong Chen [this message]
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=75dd6e6b-745d-23be-6d3d-1984b1f7f47d@intel.com \
--to=rong.a.chen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®