Content-Type: multipart/mixed; boundary="===============7954613673073659456==" MIME-Version: 1.0 From: Ye Xiaolong 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 11:14:01 +0800 Message-ID: <20180410031401.GF17893@yexl-desktop> In-Reply-To: <20180409224152.4d7fe6b7@vmware.local.home> List-Id: --===============7954613673073659456== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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: Hav= e printk come through the trace events for initcall_debug") >> >> url: https://github.com/0day-ci/linux/commits/Steven-Rostedt/init-tra= cing/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=3D0x = | 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 ecf6709= d07. > >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.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 BXPCR= SDT 00000001 BXPC 00000001) >> >> [ 0.000000] ACPI: FACP 0x000000001FFE147C 000074 (v01 BOCHS BXPCF= ACP 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 job-script # job-script is attache= d 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.129999] 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 inappropriat= e base. = Thanks, Xiaolong >-- Steve > --===============7954613673073659456==--