Date: Wed, 11 Nov 2015 19:28:31 +0100
From: Daniel J Blueman <daniel@numascale.com>
Subject: Re: [lkp] [x86/numachip] db1003a719: BUG: kernel early-boot hang
To: Ying Huang <ying.huang@linux.intel.com>
CC: <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
        Daniel Lezcano <daniel.lezcano@linaro.org>,
        Steffen Persvold <sp@numascale.com>,
        "Thomas Gleixner" <tglx@linutronix.de>
Message-ID: <1447266511.14441.1@outlook-emeawest.office365.com>
In-Reply-To: <87ziymbfos.fsf@yhuang-dev.intel.com>
References: <87ziymbfos.fsf@yhuang-dev.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Nov 2015 18:28:38.3556 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB1300
X-Microsoft-Exchange-Diagnostics: 1;AM4PR07MB1233;2:bm4IPHKchi9oqkKxZFXCvvKKV7GFiQwBmSl1FWnWqaKEPCsM01a8LwHgF/CYqicCc5L0999yLvUrTnytW1ikGHBZbUn57LgMXlRbhjeBC9IcDccuE+NHc+cWWJ5Rhu83lhm0SHF04cYuRrp1HmTo91Kqt5h78FDLN5PJOR3/qhQ=;23:76V2y1TnRNWei+oe9jCuH1TbM2UFKVIV42yoGISoFtVMsFUuJ8XRAefPhA8CUorLk8P9JuplHAQypQUtmTW0BLCbm0K1RrZX9MwO6b0UAfYH8XBcYbwJ2JmGngxgwFNog33Ha5pWeja4pJZ0QTEOYnNHz9kKXqRYCFELlFU4Jt5Yp+V/GLq0Y2g4X+UKgwsr
X-OriginatorOrg: numascale.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 3717
Lines: 71

Hi Ying Huang,

On Tue, Nov 10, 2015 at 6:12 AM, kernel test robot 
<ying.huang@linux.intel.com> wrote:
> FYI, we noticed the below changes on
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> master
> commit db1003a719d75cebe5843a7906c02c29bec9922c ("x86/numachip: 
> Cleanup Numachip support")
> 
> 
> Elapsed time: 210
> BUG: kernel early-boot hang
> Linux version 4.3.0-rc2-00001-gdb1003a #1
> Command line: root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-intel12-yocto-x86_64-14/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-allyesdebian-db1003a719d75cebe5843a7906c02c29bec9922c-20151107-100037-1jb4qfh-1.yaml 
> ARCH=x86_64 kconfig=x86_64-allyesdebian 
> branch=sergeh-security/2015-11-05/cgroupns 
> commit=db1003a719d75cebe5843a7906c02c29bec9922c 
> BOOT_IMAGE=/pkg/linux/x86_64-allyesdebian/gcc-5/db1003a719d75cebe5843a7906c02c29bec9922c/vmlinuz-4.3.0-rc2-00001-gdb1003a 
> max_uptime=600 
> RESULT_ROOT=/result/boot/1/vm-intel12-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-allyesdebian/gcc-5/db1003a719d75cebe5843a7906c02c29bec9922c/0 
> LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic 
> load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 
> vga=normal rw ip=::::vm-intel12-yocto-x86_64-14::dhcp 
> drbd.minor_count=8
> qemu-system-x86_64 -enable-kvm -cpu Nehalem -kernel 
> /pkg/linux/x86_64-allyesdebian/gcc-5/db1003a719d75cebe5843a7906c02c29bec9922c/vmlinuz-4.3.0-rc2-00001-gdb1003a 
> -append 'root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-intel12-yocto-x86_64-14/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-allyesdebian-db1003a719d75cebe5843a7906c02c29bec9922c-20151107-100037-1jb4qfh-1.yaml 
> ARCH=x86_64 kconfig=x86_64-allyesdebian 
> branch=sergeh-security/2015-11-05/cgroupns 
> commit=db1003a719d75cebe5843a7906c02c29bec9922c 
> BOOT_IMAGE=/pkg/linux/x86_64-allyesdebian/gcc-5/db1003a719d75cebe5843a7906c02c29bec9922c/vmlinuz-4.3.0-rc2-00001-gdb1003a 
> max_uptime=600 
> RESULT_ROOT=/result/boot/1/vm-intel12-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-allyesdebian/gcc-5/db1003a719d75cebe5843a7906c02c29bec9922c/0 
> LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic 
> load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 
> vga=normal rw ip=::::vm-intel12-yocto-x86_64-14::dhcp 
> drbd.minor_count=8'  -initrd 
> /fs/KVM/initrd-vm-intel12-yocto-x86_64-14 -m 832 -smp 2 -device 
> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot 
> -watchdog i6300esb -rtc base=localtime -drive 
> file=/fs/KVM/disk0-vm-intel12-yocto-x86_64-14,media=disk,if=virtio 
> -drive 
> file=/fs/KVM/disk1-vm-intel12-yocto-x86_64-14,media=disk,if=virtio 
> -pidfile /dev/shm/kboot/pid-vm-intel12-yocto-x86_64-14 -serial 
> file:/dev/shm/kboot/serial-vm-intel12-yocto-x86_64-14 -daemonize 
> -display none -monitor null

Neat, however checking out the same kernel tree at "db1003a 
x86/numachip: Cleanup Numachip support", building with the same config 
(though with GCC 5.2.1), it boots just peachy with the same args.

The patch itself is conservative, so I can't see how it could cause 
early boot hangs. Have you seen this kind of issue before, or is this 
the first time?

Thanks!
  Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/