From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [LKP] 3f906ba236 [ 71.192813] WARNING: possible circular locking dependency detected
Date: Wed, 5 Sep 2018 15:02:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1809051459130.1416@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180905090553.GA6655@shao2-debian>
On Wed, 5 Sep 2018, kernel test robot wrote:
> 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 3f906ba23689a3f824424c50f3ae937c2c70f676
> Author: Thomas Gleixner <tglx@linutronix.de>
> AuthorDate: Mon Jul 10 15:50:09 2017 -0700
> Commit: Linus Torvalds <torvalds@linux-foundation.org>
> CommitDate: Mon Jul 10 16:32:33 2017 -0700
So it identified a more than one year old commit. Great.
> vm86 returned ENOSYS, marking as inactive. 20044 iterations. [F:14867 S:5032 HI:3700] [ 57.651003] synth uevent: /module/pcmcia_core: unknown uevent action string [ 71.189062] [ 71.191953] ====================================================== [ 71.192813] WARNING: possible circular locking dependency detected [ 71.193664] 4.12.0-10480-g3f906ba #1 Not tainted [ 71.194355] ------------------------------------------------------ [ 71.195211] trinity-c0/1666 is trying to acquire lock: [ 71.195958] (mem_hotplug_lock.rw_sem){.+.+.+}, at: show_slab_objects+0x14b/0x440 [ 71.197284] [ 71.197284] but task is already holding lock:
along with completely unparseable information. What am I supposed to do
with this mail?
Thanks,
tglx
next prev parent reply other threads:[~2018-09-05 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 9:05 kernel test robot
2018-09-05 13:02 ` Thomas Gleixner [this message]
2018-09-06 0:37 ` Rong Chen
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.1809051459130.1416@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=peterz@infradead.org \
--cc=rong.a.chen@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