From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756905AbcGZPOq (ORCPT ); Tue, 26 Jul 2016 11:14:46 -0400 Received: from mga01.intel.com ([192.55.52.88]:24814 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756066AbcGZPOo (ORCPT ); Tue, 26 Jul 2016 11:14:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,425,1464678000"; d="scan'208";a="853827460" Date: Tue, 26 Jul 2016 23:13:44 +0800 From: Fengguang Wu To: "Eric W. Biederman" Cc: containers@lists.linux-foundation.org, lkp@01.org, LKML Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed Message-ID: <20160726151344.GB8811@wfg-t540p.sh.intel.com> References: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> <877fc9a6mb.fsf@x220.int.ebiederm.org> <20160726143545.GA23656@wfg-t540p.sh.intel.com> <87vazsv4cn.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <87vazsv4cn.fsf@x220.int.ebiederm.org> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 26, 2016 at 09:52:40AM -0500, Eric W. Biederman wrote: >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. Yes that's the right directions to follow. We'll make the reports more understandable and the test/bisects more reliable. In particular, I suspect this false report might be related to QEMU watchdog. The wild guess is, if trinity touches the watchdog device by accident, it may result in the VM reset w/o any symptom. >>>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. You are welcome! Thanks, Fengguang