From: Dave Jones <davej@codemonkey.org.uk>
To: lkp@lists.01.org
Subject: Re: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 17:15:16 -0400 [thread overview]
Message-ID: <20160726211516.GA9577@codemonkey.org.uk> (raw)
In-Reply-To: <20160726151344.GB8811@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On Tue, Jul 26, 2016 at 11:13:44PM +0800, Fengguang Wu wrote:
> >> 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.
See ignore_files() in pathnames.c
Adding an entry to the blacklist there is easy enough to prove/disprove this.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@codemonkey.org.uk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
containers@lists.linux-foundation.org, lkp@01.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 17:15:16 -0400 [thread overview]
Message-ID: <20160726211516.GA9577@codemonkey.org.uk> (raw)
In-Reply-To: <20160726151344.GB8811@wfg-t540p.sh.intel.com>
On Tue, Jul 26, 2016 at 11:13:44PM +0800, Fengguang Wu wrote:
> >> 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.
See ignore_files() in pathnames.c
Adding an entry to the blacklist there is easy enough to prove/disprove this.
Dave
next prev parent reply other threads:[~2016-07-26 21:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 21:20 [fs] 54cc07a761: BUG: kernel test crashed kernel test robot
2016-07-23 21:20 ` kernel test robot
[not found] ` <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-23 21:52 ` Eric W. Biederman
2016-07-23 21:52 ` Eric W. Biederman
2016-07-23 21:52 ` Eric W. Biederman
2016-07-25 18:57 ` More information please. " Eric W. Biederman
2016-07-25 18:57 ` Eric W. Biederman
2016-07-25 18:57 ` Eric W. Biederman
[not found] ` <877fc9a6mb.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 14:35 ` [LKP] " Fengguang Wu
2016-07-26 14:35 ` Fengguang Wu
2016-07-26 14:35 ` Fengguang Wu
[not found] ` <20160726143545.GA23656-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 14:52 ` [LKP] " Eric W. Biederman
2016-07-26 14:52 ` Eric W. Biederman
2016-07-26 14:52 ` Eric W. Biederman
[not found] ` <87vazsv4cn.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 15:13 ` [LKP] " Fengguang Wu
2016-07-26 15:13 ` Fengguang Wu
2016-07-26 15:13 ` Fengguang Wu
[not found] ` <20160726151344.GB8811-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 19:50 ` [LKP] " Eric W. Biederman
2016-07-26 19:50 ` Eric W. Biederman
2016-07-26 19:50 ` Eric W. Biederman
2016-07-26 21:18 ` Dave Jones
2016-07-26 21:18 ` [LKP] " Dave Jones
[not found] ` <87wpk8p49p.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 21:18 ` Dave Jones
2016-07-26 21:15 ` Dave Jones
2016-07-26 21:15 ` Dave Jones [this message]
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=20160726211516.GA9577@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.