From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Fengguang Wu <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
lkp-JC7UmRfGjtg@public.gmane.org,
kernel test robot
<xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 09:52:40 -0500 [thread overview]
Message-ID: <87vazsv4cn.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20160726143545.GA23656-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org> (Fengguang Wu's message of "Tue, 26 Jul 2016 22:35:45 +0800")
Fengguang Wu <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:
> On Mon, Jul 25, 2016 at 01:57:00PM -0500, Eric W. Biederman wrote:
>>kernel test robot <xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:
[snip]
>>>
>>> [ 19.206454] VFS: Warning: trinity-c0 using old stat() call. Recompile your binary.
>>>
>>> Elapsed time: 70
>>> BUG: kernel test crashed
>>
>>What application generated the line "BUG: kernel test crashed."
>>What flavor of crash was this?
>
> It's a simple boot test with a quick trinity run. So there will be
> some randomness in this test.
>
> The "BUG: kernel test crashed" means the VM reboots by itself while
> the trinity test is running. If the error message is "BUG: kernel boot
> crashed" it'd mean VM abnormally reboots before any test is launched.
Is it possible to include a url pointing to a page of documentation
holding this information in your emails or alternatively a url pointing
to some source code. Just so other people don't have to ask you this
question.
>>Given the last boot test failure that was reported to me was about 10
>>commits after the problem commit I unfortunately can't take it at face
>>value that the appropriate commit has been pinpointed.
>>
>>If you could give me enough information to dig into this that would
>>be great. Otherwise I am going to have to proceed forward on the basis
>>that this is a testing robot failure, and that the people who maintain
>>the testing robot don't care enough to look after it.
>
> I queued more tests in various KVM instances and find the kernel test
> crashes can also happen in the parent commit. So it looks like a false
> report. Sorry for the noise!
>
> 81754357770ebd90 aeaa4a79ff6a5ed912b7362f20
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> 5:100 0% 5:100 dmesg.BUG:kernel_test_crashed
> :100 1% 1:100 dmesg.Mem-Info
> :100 1% 1:100 dmesg.invoked_oom-killer:gfp_mask=0x
Thank you for verifying this.
Eric
next prev parent reply other threads:[~2016-07-26 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 21:20 [fs] 54cc07a761: BUG: kernel test crashed kernel test robot
[not found] ` <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-23 21:52 ` Eric W. Biederman
2016-07-25 18:57 ` More information please. " Eric W. Biederman
[not found] ` <877fc9a6mb.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 14:35 ` [LKP] " Fengguang Wu
[not found] ` <20160726143545.GA23656-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 14:52 ` Eric W. Biederman [this message]
[not found] ` <87vazsv4cn.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 15:13 ` Fengguang Wu
[not found] ` <20160726151344.GB8811-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 19:50 ` Eric W. Biederman
[not found] ` <87wpk8p49p.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 21:18 ` Dave Jones
2016-07-26 21:15 ` Dave Jones
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=87vazsv4cn.fsf@x220.int.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lkp-JC7UmRfGjtg@public.gmane.org \
--cc=xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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