From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-parisc@vger.kernel.org, linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
intel-gfx@lists.freedesktop.org, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-input@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LKP <lkp@01.org>
Subject: Re: dad4f140ed ("Merge branch 'xarray' of .."): Mem-Info:
Date: Fri, 23 Nov 2018 19:58:03 -0800 [thread overview]
Message-ID: <20181124035803.GX3065@bombadil.infradead.org> (raw)
In-Reply-To: <5bf8a766.2eiLO6qApoh2dO55%lkp@intel.com>
On Sat, Nov 24, 2018 at 09:20:38AM +0800, 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 dad4f140edaa3f6bb452b6913d41af1ffd672e45
I think you've got the wrong bisection point, confused by other messages.
Here's the messages I think you intend to chase:
[ 155.389297] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck
for 52s!
[ 155.409004] BUG: workqueue lockup - pool cpus=0 flags=0x4 nice=0 stuck for 40
s!
[ 155.420377] Showing busy workqueues and worker pools:
[ 155.428445] workqueue events: flags=0x0
[ 155.434634] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
[ 155.437904] pending: cache_reap
[ 155.449671] workqueue events_power_efficient: flags=0x82
[ 155.458000] pwq 2: cpus=0 flags=0x4 nice=0 active=3/256
[ 155.461269] pending: neigh_periodic_work, do_cache_clean, check_lifetime
but you're getting hung up on the testsuite problems.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-24 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 1:20 dad4f140ed ("Merge branch 'xarray' of .."): Mem-Info: kernel test robot
2018-11-24 3:58 ` Matthew Wilcox [this message]
2018-11-24 9:04 ` Philip Li
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=20181124035803.GX3065@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).