From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
To: lkp@lists.01.org
Subject: Re: [x86/intel/quark] 8bbc2a135b6: WARNING: CPU: 0 PID: 1 at arch/x86/platform/intel-quark/imr.c:358 imr_add_range+0x2b4/0x370()
Date: Tue, 31 Mar 2015 10:57:42 +0100 [thread overview]
Message-ID: <551A6F96.7050102@nexus-software.ie> (raw)
In-Reply-To: <CAC=cRTOxu7mYzVzg0vQhmWp=AXLJfOkgY_1S=hCtbj=YXrgLHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
On 31/03/15 03:02, huang ying wrote:
> The qemu command line we used is as follow:
>
> qemu-system-i386 -enable-kvm -kernel
> /kernel/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/vmlinuz-4.0.0-rc5
> -append 'user=lkp
> job=/lkp/scheduled/vm-kbuild-yocto-i386-4/rand_boot-1-yocto-minimal-i386.cgz-i386-randconfig-ib0-03292200-bc465aa9d045feb0e13b4a8f32cc33c1943f62d6-0-20150329-102587-1i8stfj.yaml
> ARCH=i386
> BOOT_IMAGE=/kernel/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/vmlinuz-4.0.0-rc5
> kconfig=i386-randconfig-ib0-03292200
> commit=bc465aa9d045feb0e13b4a8f32cc33c1943f62d6 branch=linus/master
> root=/dev/ram0 max_uptime=3600
> RESULT_ROOT=/result/vm-kbuild-yocto-i386/boot/1/yocto-minimal-i386.cgz/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/0
> ip=::::vm-kbuild-yocto-i386-4::dhcp earlyprintk=ttyS0,115200
> rd.udev.log-priority=err systemd.log_target=journal
> systemd.log_level=warning 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 drbd.minor_count=8'
> -initrd /fs/sda1/initrd-vm-kbuild-yocto-i386-4 -m 320 -smp 2 -net
> nic,vlan=1,model=e1000 -net user,vlan=1 -boot order=nc -no-reboot
> -watchdog i6300esb -rtc base=localtime -drive
> file=/fs/sda1/disk0-vm-kbuild-yocto-i386-4,media=disk,if=virtio -pidfile
> /dev/shm/kboot/pid-vm-kbuild-yocto-i386-4 -serial
> file:/dev/shm/kboot/serial-vm-kbuild-yocto-i386-4 -daemonize -display
> none -monitor null
Thanks.
Replicated - have a patch ready :)
WARNING: multiple messages have this Message-ID (diff)
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [x86/intel/quark] 8bbc2a135b6: WARNING: CPU: 0 PID: 1 at arch/x86/platform/intel-quark/imr.c:358 imr_add_range+0x2b4/0x370()
Date: Tue, 31 Mar 2015 10:57:42 +0100 [thread overview]
Message-ID: <551A6F96.7050102@nexus-software.ie> (raw)
In-Reply-To: <CAC=cRTOxu7mYzVzg0vQhmWp=AXLJfOkgY_1S=hCtbj=YXrgLHA@mail.gmail.com>
On 31/03/15 03:02, huang ying wrote:
> The qemu command line we used is as follow:
>
> qemu-system-i386 -enable-kvm -kernel
> /kernel/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/vmlinuz-4.0.0-rc5
> -append 'user=lkp
> job=/lkp/scheduled/vm-kbuild-yocto-i386-4/rand_boot-1-yocto-minimal-i386.cgz-i386-randconfig-ib0-03292200-bc465aa9d045feb0e13b4a8f32cc33c1943f62d6-0-20150329-102587-1i8stfj.yaml
> ARCH=i386
> BOOT_IMAGE=/kernel/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/vmlinuz-4.0.0-rc5
> kconfig=i386-randconfig-ib0-03292200
> commit=bc465aa9d045feb0e13b4a8f32cc33c1943f62d6 branch=linus/master
> root=/dev/ram0 max_uptime=3600
> RESULT_ROOT=/result/vm-kbuild-yocto-i386/boot/1/yocto-minimal-i386.cgz/i386-randconfig-ib0-03292200/bc465aa9d045feb0e13b4a8f32cc33c1943f62d6/0
> ip=::::vm-kbuild-yocto-i386-4::dhcp earlyprintk=ttyS0,115200
> rd.udev.log-priority=err systemd.log_target=journal
> systemd.log_level=warning 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 drbd.minor_count=8'
> -initrd /fs/sda1/initrd-vm-kbuild-yocto-i386-4 -m 320 -smp 2 -net
> nic,vlan=1,model=e1000 -net user,vlan=1 -boot order=nc -no-reboot
> -watchdog i6300esb -rtc base=localtime -drive
> file=/fs/sda1/disk0-vm-kbuild-yocto-i386-4,media=disk,if=virtio -pidfile
> /dev/shm/kboot/pid-vm-kbuild-yocto-i386-4 -serial
> file:/dev/shm/kboot/serial-vm-kbuild-yocto-i386-4 -daemonize -display
> none -monitor null
Thanks.
Replicated - have a patch ready :)
next prev parent reply other threads:[~2015-03-31 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 6:28 [x86/intel/quark] 8bbc2a135b6: WARNING: CPU: 0 PID: 1 at arch/x86/platform/intel-quark/imr.c:358 imr_add_range+0x2b4/0x370() Huang Ying
2015-03-30 6:28 ` [LKP] " Huang Ying
2015-03-30 8:15 ` Bryan O'Donoghue
2015-03-30 8:15 ` [LKP] " Bryan O'Donoghue
2015-03-30 14:39 ` Bryan O'Donoghue
2015-03-31 2:02 ` huang ying
2015-03-31 9:57 ` Bryan O'Donoghue [this message]
2015-03-31 9:57 ` [LKP] " Bryan O'Donoghue
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=551A6F96.7050102@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--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.