From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756811AbcGZPGP (ORCPT ); Tue, 26 Jul 2016 11:06:15 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:40602 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752871AbcGZPGO (ORCPT ); Tue, 26 Jul 2016 11:06:14 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Fengguang Wu Cc: kernel test robot , containers@lists.linux-foundation.org, lkp@01.org, LKML References: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> <877fc9a6mb.fsf@x220.int.ebiederm.org> <20160726143545.GA23656@wfg-t540p.sh.intel.com> Date: Tue, 26 Jul 2016 09:52:40 -0500 In-Reply-To: <20160726143545.GA23656@wfg-t540p.sh.intel.com> (Fengguang Wu's message of "Tue, 26 Jul 2016 22:35:45 +0800") Message-ID: <87vazsv4cn.fsf@x220.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1bS3vp-0007sv-8z;;;mid=<87vazsv4cn.fsf@x220.int.ebiederm.org>;;;hst=in02.mta.xmission.com;;;ip=67.3.204.119;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1/0zAJS4Ek4Pc/EXgh/gpgTX6PMPp+Ir0Y= X-SA-Exim-Connect-IP: 67.3.204.119 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.7 XMSubLong Long Subject * 0.0 TVD_RCVD_IP Message was received from an IP address * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa07 1397; Body=1 Fuz1=1 Fuz2=1] X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Fengguang Wu X-Spam-Relay-Country: X-Spam-Timing: total 592 ms - load_scoreonly_sql: 0.09 (0.0%), signal_user_changed: 5 (0.9%), b_tie_ro: 2.9 (0.5%), parse: 2.5 (0.4%), extract_message_metadata: 22 (3.7%), get_uri_detail_list: 2.6 (0.4%), tests_pri_-1000: 5 (0.9%), tests_pri_-950: 1.94 (0.3%), tests_pri_-900: 1.57 (0.3%), tests_pri_-400: 49 (8.3%), check_bayes: 48 (8.1%), b_tokenize: 10 (1.7%), b_tok_get_all: 14 (2.4%), b_comp_prob: 3.9 (0.7%), b_tok_touch_all: 16 (2.7%), b_finish: 0.70 (0.1%), tests_pri_0: 423 (71.4%), check_dkim_signature: 0.90 (0.2%), check_dkim_adsp: 44 (7.4%), tests_pri_500: 75 (12.6%), poll_dns_idle: 64 (10.8%), rewrite_mail: 0.00 (0.0%) Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fengguang Wu writes: > On Mon, Jul 25, 2016 at 01:57:00PM -0500, Eric W. Biederman wrote: >>kernel test robot 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