From: Borislav Petkov <bp@alien8.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Ye Xiaolong <xiaolong.ye@intel.com>, X86 ML <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [x86] ed3ce2a917: BUG:unable_to_handle_kernel
Date: Thu, 9 Mar 2017 09:17:36 +0100 [thread overview]
Message-ID: <20170309081736.7jbbbcjwehjnhjwg@pd.tnic> (raw)
In-Reply-To: <20170309023052.grzkmd2m6cttnesv@wfg-t540p.sh.intel.com>
On Thu, Mar 09, 2017 at 10:30:52AM +0800, Fengguang Wu wrote:
> One possible improvement is to provide "lkp qemu" reproduce steps for
> kernel oops -- it would be way more convenient and safe to follow than
> "lkp run", since the later risks hang the physical machine.
Right, that would mean that the bug should be triggerable in qemu. Some
bugs happen on baremetal only though.
> As for the test description, the dmesg carries markers for the user
> space test start/stop points, so the robot can easily tell whether the
> oops happen during the test or before/after the test -- the latter may
> well (but not always) indicate the oops is not relevant to the testcase,
> but to the regular kernel boot/reboot/kexec process.
Right, if that is made part of the report, it would make the reports
better. Something like: "this happens when preparing our test env" or
"this happens while running this test blabla".
Thanks guys and keep up the good work!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-03-09 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:51 [PATCH] x86: Optimize clear_page() Borislav Petkov
2017-02-15 11:19 ` [PATCH -v1.1] " Borislav Petkov
2017-02-19 13:41 ` Borislav Petkov
2017-03-01 9:47 ` [tip:x86/asm] x86/asm: " tip-bot for Borislav Petkov
2017-03-07 5:11 ` Yinghai Lu
2017-03-07 7:30 ` Ingo Molnar
2017-03-07 18:57 ` Yinghai Lu
2017-03-08 10:47 ` Ingo Molnar
2017-03-02 1:09 ` [lkp-robot] [x86] ed3ce2a917: BUG:unable_to_handle_kernel kernel test robot
2017-03-02 18:19 ` Borislav Petkov
2017-03-09 2:13 ` Ye Xiaolong
2017-03-09 2:30 ` Fengguang Wu
2017-03-09 8:17 ` Borislav Petkov [this message]
2017-03-09 8:14 ` Borislav Petkov
2017-03-10 2:33 ` Ye Xiaolong
2017-03-10 8:30 ` Borislav Petkov
2017-03-07 8:34 ` [tip:x86/asm] x86/asm: Optimize clear_page() tip-bot for Borislav Petkov
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=20170309081736.7jbbbcjwehjnhjwg@pd.tnic \
--to=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=xiaolong.ye@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).