Re: [x86/topology] 6a1447190e: BUG: unable to handle kernel paging request at ffffffffffffffff

From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/topology] 6a1447190e: BUG: unable to handle kernel paging request at ffffffffffffffff
Date: Fri, 26 Feb 2016 16:36:38 +0800	[thread overview]
Message-ID: <87a8mn7trd.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1602260854030.3638@nanos>

[-- Attachment #1: Type: text/plain, Size: 3483 bytes --]

Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 26 Feb 2016, kernel test robot wrote:
>> FYI, we noticed the below changes on
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core
>> commit 6a1447190e7f7540be17414db801ac6a12d77566 ("x86/topology: Create logical package id")
>> 
>> [    4.686741] smpboot: Total of 160 processors activated (936319.36 BogoMIPS)
>> [    5.326197] BUG: unable to handle kernel paging request at ffffffffffffffff
>> [    5.328153] IP: [<ffffffff81211303>] __kmalloc_track_caller+0x106/0x1cb
>
> I have no idea how that is related.
>
>> To reproduce:
>> 
>>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>>         cd lkp-tests
>>         bin/lkp install job.yaml  # job file is attached in this email
>>         bin/lkp run     job.yaml
>
> I finally gave it a try and to be honest it's completely useless.
>
> root(a)herakles:/home/tglx/work/kernel/lkp/lkp-tests# bin/lkp install job.yaml
>
>   Creating testbox configuration file: /home/tglx/work/kernel/lkp/lkp-tests/hosts/herakles.
>   /home/tglx/work/kernel/lkp/lkp-tests/lkp-exec/install: 87: /home/tglx/work/kernel/lkp/lkp-tests/lkp-exec/install: Bad substitution
>
> Which is not a surprise as neither hdd_partitions nor ssd_partitions can be
> evaluated.
>
> After creating that config file manually I run the job:
>
> # bin/lkp run     job.yaml 
> wait for background monitors: oom-killer watchdog
>
> That returns after roughly 1 second doing nothing w/o any result.

Sorry, the reproduce steps in the original email is not correct.  In
fact, this is a boot error even before the user space run.  The qemu
command line i demsg.xz attached in the original email may help producing.

qemu-system-x86_64 -enable-kvm -kernel /pkg/linux/x86_64-lkp/gcc-4.9/6a1447190e7f7540be17414db801ac6a12d77566/vmlinuz-4.5.0-rc4-00211-g6a14471 -append 'root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-client7-1G-3/bisect_locktorture-300s-debian-x86_64-2015-02-07.cgz-x86_64-lkp-6a1447190e7f7540be17414db801ac6a12d77566-20160225-17029-1yepae-0.yaml ARCH=x86_64 kconfig=x86_64-lkp branch=linux-devel/devel-catchup-201602250443 commit=6a1447190e7f7540be17414db801ac6a12d77566 BOOT_IMAGE=/pkg/linux/x86_64-lkp/gcc-4.9/6a1447190e7f7540be17414db801ac6a12d77566/vmlinuz-4.5.0-rc4-00211-g6a14471 max_uptime=1500 RESULT_ROOT=/result/locktorture/300s/vm-client7-1G/debian-x86_64-2015-02-07.cgz/x86_64-lkp/gcc-4.9/6a1447190e7f7540be17414db801ac6a12d77566/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-client7-1G-3::dhcp'  -initrd /fs/sda3/initrd-vm-client7-1G-3 -m 1024 -smp 160 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::23502-:22 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime -drive file=/fs/sda3/disk0-vm-client7-1G-3,media=disk,if=virtio -drive file=/fs/sda3/disk1-vm-client7-1G-3,media=disk,if=virtio -pidfile /dev/shm/kboot/pid-vm-client7-1G-3 -serial file:/dev/shm/kboot/serial-vm-client7-1G-3 -daemonize -display none -monitor null 

Best Regards,
Huang, Ying

> Thanks,
>
> 	tglx
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp