From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage
Date: Tue, 10 Apr 2018 09:23:40 +0800 [thread overview]
Message-ID: <20180410012340.GA17893@yexl-desktop> (raw)
In-Reply-To: <20180409180454.1310abea@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 2837 bytes --]
Hi, Steven
On 04/09, Steven Rostedt wrote:
>On Mon, 9 Apr 2018 13:32:52 +0800
>kernel test robot <xiaolong.ye@intel.com> wrote:
>
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have printk come through the trace events for initcall_debug")
>> url: https://github.com/0day-ci/linux/commits/Steven-Rostedt/init-tracing/20180407-130743
>>
>>
>> in testcase: boot
>>
>> on test machine: qemu-system-x86_64 -enable-kvm -cpu Nehalem -smp 2 -m 512M
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>> +------------------------------------------------------------------+------------+------------+
>> | | ecf6709d07 | 2580d6b795 |
>> +------------------------------------------------------------------+------------+------------+
>> | boot_successes | 0 | 0 |
>> | boot_failures | 8 | 8 |
>> | invoked_oom-killer:gfp_mask=0x | 8 | |
>> | Mem-Info | 8 | |
>> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 8 | |
>> | BUG:kernel_reboot-without-warning_in_boot_stage | 0 | 8 |
>> +------------------------------------------------------------------+------------+------------+
>
>What does this mean?
It means BUG:BUG:kernel_reboot-without-warning_in_boot_stage occurred 8 times
in boot tests for commit 2580d6b795, while 0 time for its parent ecf6709d07.
>
>>
>>
>>
>> [ 0.000000] RAMDISK: [mem 0x1b7e2000-0x1ffcffff]
>> [ 0.000000] ACPI: Early table checksum verification disabled
>> [ 0.000000] ACPI: RSDP 0x00000000000F6860 000014 (v00 BOCHS )
>> [ 0.000000] ACPI: RSDT 0x000000001FFE1628 000030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
>> [ 0.000000] ACPI: FACP 0x000000001FFE147C 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
>> BUG: kernel reboot-without-warning in boot stage
>>
>> Elapsed time: 10
>>
>> #!/bin/bash
>>
>>
>>
>> To reproduce:
>>
>> git clone https://github.com/intel/lkp-tests.git
>> cd lkp-tests
>> bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
>>
>
>The config boots fine for me. But I don't have the setup to run the
>above and get it to work, nor the time to figure out why it doesn't
>work.
Could you paste your failure log here, we can see if there is something we can help.
Thanks,
Xiaolong
>
>-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage
Date: Tue, 10 Apr 2018 09:23:40 +0800 [thread overview]
Message-ID: <20180410012340.GA17893@yexl-desktop> (raw)
In-Reply-To: <20180409180454.1310abea@gandalf.local.home>
Hi, Steven
On 04/09, Steven Rostedt wrote:
>On Mon, 9 Apr 2018 13:32:52 +0800
>kernel test robot <xiaolong.ye@intel.com> wrote:
>
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have printk come through the trace events for initcall_debug")
>> url: https://github.com/0day-ci/linux/commits/Steven-Rostedt/init-tracing/20180407-130743
>>
>>
>> in testcase: boot
>>
>> on test machine: qemu-system-x86_64 -enable-kvm -cpu Nehalem -smp 2 -m 512M
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>> +------------------------------------------------------------------+------------+------------+
>> | | ecf6709d07 | 2580d6b795 |
>> +------------------------------------------------------------------+------------+------------+
>> | boot_successes | 0 | 0 |
>> | boot_failures | 8 | 8 |
>> | invoked_oom-killer:gfp_mask=0x | 8 | |
>> | Mem-Info | 8 | |
>> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 8 | |
>> | BUG:kernel_reboot-without-warning_in_boot_stage | 0 | 8 |
>> +------------------------------------------------------------------+------------+------------+
>
>What does this mean?
It means BUG:BUG:kernel_reboot-without-warning_in_boot_stage occurred 8 times
in boot tests for commit 2580d6b795, while 0 time for its parent ecf6709d07.
>
>>
>>
>>
>> [ 0.000000] RAMDISK: [mem 0x1b7e2000-0x1ffcffff]
>> [ 0.000000] ACPI: Early table checksum verification disabled
>> [ 0.000000] ACPI: RSDP 0x00000000000F6860 000014 (v00 BOCHS )
>> [ 0.000000] ACPI: RSDT 0x000000001FFE1628 000030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
>> [ 0.000000] ACPI: FACP 0x000000001FFE147C 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
>> BUG: kernel reboot-without-warning in boot stage
>>
>> Elapsed time: 10
>>
>> #!/bin/bash
>>
>>
>>
>> To reproduce:
>>
>> git clone https://github.com/intel/lkp-tests.git
>> cd lkp-tests
>> bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
>>
>
>The config boots fine for me. But I don't have the setup to run the
>above and get it to work, nor the time to figure out why it doesn't
>work.
Could you paste your failure log here, we can see if there is something we can help.
Thanks,
Xiaolong
>
>-- Steve
next prev parent reply other threads:[~2018-04-10 1:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 19:08 [PATCH 0/4 v2] init, tracing: Steven Rostedt
2018-04-06 19:08 ` [PATCH 1/4 v2] init, tracing: Add initcall trace events Steven Rostedt
2018-04-06 19:08 ` [PATCH 2/4 v2] init, tracing: instrument security and console " Steven Rostedt
2018-04-06 19:08 ` [PATCH 3/4 v2] init, tracing: Have printk come through the trace events for initcall_debug Steven Rostedt
2018-04-09 5:32 ` [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage kernel test robot
2018-04-09 5:32 ` kernel test robot
2018-04-09 22:04 ` Steven Rostedt
2018-04-09 22:04 ` Steven Rostedt
2018-04-10 1:23 ` Ye Xiaolong [this message]
2018-04-10 1:23 ` Ye Xiaolong
2018-04-10 2:41 ` Steven Rostedt
2018-04-10 2:41 ` Steven Rostedt
2018-04-10 3:14 ` Ye Xiaolong
2018-04-10 3:14 ` Ye Xiaolong
2018-04-06 19:08 ` [PATCH 4/4 v2] init: Have initcall_debug still work without CONFIG_TRACEPOINTS Steven Rostedt
2018-04-07 8:18 ` kbuild test robot
2018-04-06 19:16 ` [PATCH 0/4 v2] init, tracing: Add initcall trace events Steven Rostedt
2018-04-06 19:19 ` Steven Rostedt
2018-04-06 19:34 ` Peter Zijlstra
2018-04-06 19:46 ` Steven Rostedt
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=20180410012340.GA17893@yexl-desktop \
--to=xiaolong.ye@intel.com \
--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.