Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Ye Xiaolong]

On 04/09, Steven Rostedt wrote:
>On Tue, 10 Apr 2018 09:23:40 +0800
>Ye Xiaolong  wrote:
>
>> Hi, Steven
>> 
>> On 04/09, Steven Rostedt wrote:
>> >On Mon, 9 Apr 2018 13:32:52 +0800
>> >kernel test robot  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.
>
>I don't have a commit 2580d6b795.
>
>The commit with the title "init, tracing: Have printk come through the
>trace events for initcall_debug" is 4e37958d1288ce. linux-next doesn't
>have that commit sha1 either.

This commit was generated by 0day service, it captured your email patchset 
which posted
on LKML and then applied it on top of 06dd3dfeea60 and performed build/boot 
tests accordingly.

>
>
>> 
>> >  
>> >> 
>> >> 
>> >> 
>> >> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
>> >> [0.00] ACPI: Early table checksum verification disabled
>> >> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
>> >> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
>> >> 0001 BXPC 0001)
>> >> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
>> >> 0001 BXPC 0001)
>> >> 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  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.
>
>I tried it on a more up-to-date box, after checking out my commit with
>the title you say is an error. I compiled your config with gcc (GCC)
>7.3.1 20180130 (Red Hat 7.3.1-2), and ran the above (which did work).
>It ended after it got to a login prompt.
>
>---
>[..]
>[   10.588029] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>[   10.589363] platform regulatory.0: Direct firmware load for regulatory.db 
>failed with error -2
>[   10.590385] cfg80211: failed to load regulatory.db
>[   10.610002] Freeing unused kernel memory: 1980K
>[   10.610533] Write protecting the kernel read-only data: 49152k
>[   10.615728] Freeing unused kernel memory: 2028K
>[   10.620754] Freeing unused kernel memory: 464K
>INIT: version 2.88 booting
>/etc/rcS.d/S00fbsetup: line 3: /sbin/modprobe: not found
>
>Please wait: booting...
>[   10.676861] rc (151) used greatest stack depth: 27848 bytes left
>Starting udev
>[   10.750281] udevd[175]: starting version 3.1.5
>[   10.759923] udevd (175) used greatest stack depth: 27696 bytes left
>[   11.12] udevadm (178) used greatest stack depth: 26696 bytes left
>Populating dev cache
>INIT: Entering runlevel: 5
>Configuring network interfaces... done.
>Starting syslogd/klogd: done
>
>Poky (Yocto Project Reference Distro) 2.1 qemux86-64 /dev/ttyS0
>
>qemux86-64 login:
>---
>
>What am I suppose to see?
>

So I figure the gap may be 0day bot applied your patchset to a inappropriate 

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Ye Xiaolong]

On 04/09, Steven Rostedt wrote:
>On Tue, 10 Apr 2018 09:23:40 +0800
>Ye Xiaolong  wrote:
>
>> Hi, Steven
>> 
>> On 04/09, Steven Rostedt wrote:
>> >On Mon, 9 Apr 2018 13:32:52 +0800
>> >kernel test robot  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.
>
>I don't have a commit 2580d6b795.
>
>The commit with the title "init, tracing: Have printk come through the
>trace events for initcall_debug" is 4e37958d1288ce. linux-next doesn't
>have that commit sha1 either.

This commit was generated by 0day service, it captured your email patchset 
which posted
on LKML and then applied it on top of 06dd3dfeea60 and performed build/boot 
tests accordingly.

>
>
>> 
>> >  
>> >> 
>> >> 
>> >> 
>> >> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
>> >> [0.00] ACPI: Early table checksum verification disabled
>> >> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
>> >> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
>> >> 0001 BXPC 0001)
>> >> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
>> >> 0001 BXPC 0001)
>> >> 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  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.
>
>I tried it on a more up-to-date box, after checking out my commit with
>the title you say is an error. I compiled your config with gcc (GCC)
>7.3.1 20180130 (Red Hat 7.3.1-2), and ran the above (which did work).
>It ended after it got to a login prompt.
>
>---
>[..]
>[   10.588029] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>[   10.589363] platform regulatory.0: Direct firmware load for regulatory.db 
>failed with error -2
>[   10.590385] cfg80211: failed to load regulatory.db
>[   10.610002] Freeing unused kernel memory: 1980K
>[   10.610533] Write protecting the kernel read-only data: 49152k
>[   10.615728] Freeing unused kernel memory: 2028K
>[   10.620754] Freeing unused kernel memory: 464K
>INIT: version 2.88 booting
>/etc/rcS.d/S00fbsetup: line 3: /sbin/modprobe: not found
>
>Please wait: booting...
>[   10.676861] rc (151) used greatest stack depth: 27848 bytes left
>Starting udev
>[   10.750281] udevd[175]: starting version 3.1.5
>[   10.759923] udevd (175) used greatest stack depth: 27696 bytes left
>[   11.12] udevadm (178) used greatest stack depth: 26696 bytes left
>Populating dev cache
>INIT: Entering runlevel: 5
>Configuring network interfaces... done.
>Starting syslogd/klogd: done
>
>Poky (Yocto Project Reference Distro) 2.1 qemux86-64 /dev/ttyS0
>
>qemux86-64 login:
>---
>
>What am I suppose to see?
>

So I figure the gap may be 0day bot applied your patchset to a inappropriate 
base. 

Thanks,
Xiaolong
>-- Steve
>

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Steven Rostedt]

On Tue, 10 Apr 2018 09:23:40 +0800
Ye Xiaolong  wrote:

> Hi, Steven
> 
> On 04/09, Steven Rostedt wrote:
> >On Mon, 9 Apr 2018 13:32:52 +0800
> >kernel test robot  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.

I don't have a commit 2580d6b795.

The commit with the title "init, tracing: Have printk come through the
trace events for initcall_debug" is 4e37958d1288ce. linux-next doesn't
have that commit sha1 either.


> 
> >  
> >> 
> >> 
> >> 
> >> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
> >> [0.00] ACPI: Early table checksum verification disabled
> >> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
> >> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
> >> 0001 BXPC 0001)
> >> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
> >> 0001 BXPC 0001)
> >> 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  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.

I tried it on a more up-to-date box, after checking out my commit with
the title you say is an error. I compiled your config with gcc (GCC)
7.3.1 20180130 (Red Hat 7.3.1-2), and ran the above (which did work).
It ended after it got to a login prompt.

---
[..]
[   10.588029] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.589363] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[   10.590385] cfg80211: failed to load regulatory.db
[   10.610002] Freeing unused kernel memory: 1980K
[   10.610533] Write protecting the kernel read-only data: 49152k
[   10.615728] Freeing unused kernel memory: 2028K
[   10.620754] Freeing unused kernel memory: 464K
INIT: version 2.88 booting
/etc/rcS.d/S00fbsetup: line 3: /sbin/modprobe: not found

Please wait: booting...
[   10.676861] rc (151) used greatest stack depth: 27848 bytes left
Starting udev
[   10.750281] udevd[175]: starting version 3.1.5
[   10.759923] udevd (175) used greatest stack depth: 27696 bytes left
[   11.12] udevadm (178) used greatest stack depth: 26696 bytes left
Populating dev cache
INIT: Entering runlevel: 5
Configuring network interfaces... done.
Starting syslogd/klogd: done

Poky (Yocto Project Reference Distro) 2.1 qemux86-64 /dev/ttyS0

qemux86-64 login:
---

What am I suppose to see?

-- Steve

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Steven Rostedt]

On Tue, 10 Apr 2018 09:23:40 +0800
Ye Xiaolong  wrote:

> Hi, Steven
> 
> On 04/09, Steven Rostedt wrote:
> >On Mon, 9 Apr 2018 13:32:52 +0800
> >kernel test robot  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.

I don't have a commit 2580d6b795.

The commit with the title "init, tracing: Have printk come through the
trace events for initcall_debug" is 4e37958d1288ce. linux-next doesn't
have that commit sha1 either.


> 
> >  
> >> 
> >> 
> >> 
> >> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
> >> [0.00] ACPI: Early table checksum verification disabled
> >> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
> >> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
> >> 0001 BXPC 0001)
> >> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
> >> 0001 BXPC 0001)
> >> 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  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.

I tried it on a more up-to-date box, after checking out my commit with
the title you say is an error. I compiled your config with gcc (GCC)
7.3.1 20180130 (Red Hat 7.3.1-2), and ran the above (which did work).
It ended after it got to a login prompt.

---
[..]
[   10.588029] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.589363] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[   10.590385] cfg80211: failed to load regulatory.db
[   10.610002] Freeing unused kernel memory: 1980K
[   10.610533] Write protecting the kernel read-only data: 49152k
[   10.615728] Freeing unused kernel memory: 2028K
[   10.620754] Freeing unused kernel memory: 464K
INIT: version 2.88 booting
/etc/rcS.d/S00fbsetup: line 3: /sbin/modprobe: not found

Please wait: booting...
[   10.676861] rc (151) used greatest stack depth: 27848 bytes left
Starting udev
[   10.750281] udevd[175]: starting version 3.1.5
[   10.759923] udevd (175) used greatest stack depth: 27696 bytes left
[   11.12] udevadm (178) used greatest stack depth: 26696 bytes left
Populating dev cache
INIT: Entering runlevel: 5
Configuring network interfaces... done.
Starting syslogd/klogd: done

Poky (Yocto Project Reference Distro) 2.1 qemux86-64 /dev/ttyS0

qemux86-64 login:
---

What am I suppose to see?

-- Steve

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Ye Xiaolong]

Hi, Steven

On 04/09, Steven Rostedt wrote:
>On Mon, 9 Apr 2018 13:32:52 +0800
>kernel test robot  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.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
>> [0.00] ACPI: Early table checksum verification disabled
>> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
>> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
>> 0001 BXPC 0001)
>> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
>> 0001 BXPC 0001)
>> 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  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

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Ye Xiaolong]

Hi, Steven

On 04/09, Steven Rostedt wrote:
>On Mon, 9 Apr 2018 13:32:52 +0800
>kernel test robot  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.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
>> [0.00] ACPI: Early table checksum verification disabled
>> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
>> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
>> 0001 BXPC 0001)
>> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
>> 0001 BXPC 0001)
>> 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  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

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Steven Rostedt]

On Mon, 9 Apr 2018 13:32:52 +0800
kernel test robot  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?

> 
> 
> 
> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
> [0.00] ACPI: Early table checksum verification disabled
> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
> 0001 BXPC 0001)
> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
> 0001 BXPC 0001)
> 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  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.

-- Steve

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[Steven Rostedt]

On Mon, 9 Apr 2018 13:32:52 +0800
kernel test robot  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?

> 
> 
> 
> [0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
> [0.00] ACPI: Early table checksum verification disabled
> [0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
> [0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
> 0001 BXPC 0001)
> [0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
> 0001 BXPC 0001)
> 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  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.

-- Steve

[lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[kernel test robot]

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  |
+--+++



[0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
[0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
0001 BXPC 0001)
[0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
0001 BXPC 0001)
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  job-script  # job-script is attached in this 
email



Thanks,
Xiaolong
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.16.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=28
CONFIG_ARCH_MMAP_RND_BITS_MAX=32
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_KASAN_SHADOW_OFFSET=0xdc00
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
CONFIG_KERNEL_LZO=y
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y
CONFIG_GENERIC_IRQ_RESERVATION_MODE=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_DEBUGFS=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not 

[lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

[kernel test robot]

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  |
+--+++



[0.00] RAMDISK: [mem 0x1b7e2000-0x1ffc]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F6860 14 (v00 BOCHS )
[0.00] ACPI: RSDT 0x1FFE1628 30 (v01 BOCHS  BXPCRSDT 
0001 BXPC 0001)
[0.00] ACPI: FACP 0x1FFE147C 74 (v01 BOCHS  BXPCFACP 
0001 BXPC 0001)
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  job-script  # job-script is attached in this 
email



Thanks,
Xiaolong
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.16.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=28
CONFIG_ARCH_MMAP_RND_BITS_MAX=32
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_KASAN_SHADOW_OFFSET=0xdc00
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
CONFIG_KERNEL_LZO=y
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y
CONFIG_GENERIC_IRQ_RESERVATION_MODE=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_DEBUGFS=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not