From: Rong Chen <rong.a.chen@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [LKP] 5404a7f1c2 [ 90.902541] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]
Date: Wed, 19 Dec 2018 18:03:45 +0800 [thread overview]
Message-ID: <38ee8a35-1bb3-7a63-8ef6-75f0ff46d198@intel.com> (raw)
In-Reply-To: <20181218121710.GT10600@bombadil.infradead.org>
On 12/18/2018 08:17 PM, Matthew Wilcox wrote:
> On Tue, Dec 18, 2018 at 08:20:28AM +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 5404a7f1c21cfda061712bedf2d06cc0f6c755e9
> I feel like you're wasting my time. This is the fourth time in a row
> you've reported something I can't reproduce. At least this time the
> instructions work, but I've tried it a dozen times and it doesn't produce
> the error you're showing.
>
> $ git branch
> * (HEAD detached at 5404a7f1c21c)
> ...
> [ 0.000000] Linux version 4.20.0-rc1-00012-g5404a7f1c21c (willy@bobo) (gcc version 8.2.0 (Debian 8.2.0-9)) #4 Mon Dec 17 23:28:21 EST 2018
> ...
> [ 9.848471] test_uuid: all 18 tests passed
> [ 11.019267] XArray: 19496249 of 19496249 tests passed
>
> Your logs show it failing every time. I can't help but wonder if it's
> something else in your setup that's causing it to fail -- maybe the
> machines doing the testing are overloaded?
Please accept my apologies for taking your time, it might be a false
positive,
we have uploaded the original
bzImage(https://download.01.org/0day-ci/lkp-qemu/fbc/5404a7f1c21cfda061712bedf2d06cc0f6c755e9/)
for your reference.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2018-12-19 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 0:20 kernel test robot
2018-12-18 12:17 ` Matthew Wilcox
2018-12-19 10:03 ` Rong Chen [this message]
2018-12-19 12:42 ` Matthew Wilcox
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=38ee8a35-1bb3-7a63-8ef6-75f0ff46d198@intel.com \
--to=rong.a.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=willy@infradead.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
Powered by JetHome