All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 30 Mar 2015 09:15:06 +0100	[thread overview]
Message-ID: <5519060A.3080909@nexus-software.ie> (raw)
In-Reply-To: <1427696929.17170.82.camel@intel.com>

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


> [    0.752570]  [<c1ab0845>] dump_stack+0x16/0x18
> [    0.752570]  [<c1ab0845>] dump_stack+0x16/0x18
> [    0.753420]  [<c103bb27>] warn_slowpath_common+0x87/0xc0
> [    0.753420]  [<c103bb27>] warn_slowpath_common+0x87/0xc0
> [    0.754429]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.754429]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.755384]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.755384]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.756335]  [<c103bbc3>] warn_slowpath_fmt+0x33/0x40
> [    0.756335]  [<c103bbc3>] warn_slowpath_fmt+0x33/0x40
> [    0.757293]  [<c1038674>] imr_add_range+0x2b4/0x370
> [    0.757293]  [<c1038674>] imr_add_range+0x2b4/0x370
> [    0.758219]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.758219]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.759200]  [<c103209a>] ? __phys_addr+0x3a/0x90
> [    0.759200]  [<c103209a>] ? __phys_addr+0x3a/0x90
> [    0.760090]  [<c106e4de>] ? debug_check_no_locks_freed+0x9e/0x160
> [    0.760090]  [<c106e4de>] ? debug_check_no_locks_freed+0x9e/0x160
> [    0.761361]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.761361]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.762419]  [<c1fb836a>] imr_self_test_init+0x40/0x1d9
> [    0.762419]  [<c1fb836a>] imr_self_test_init+0x40/0x1d9
> [    0.763439]  [<c1fb832a>] ? imr_self_test_result+0x4e/0x4e
> [    0.763439]  [<c1fb832a>] ? imr_self_test_result+0x4e/0x4e
> [    0.764477]  [<c1fa7d03>] do_one_initcall+0x180/0x193
> [    0.764477]  [<c1fa7d03>] do_one_initcall+0x180/0x193
> [    0.765443]  [<c10568bb>] ? parse_args+0x25b/0x530
> [    0.765443]  [<c10568bb>] ? parse_args+0x25b/0x530
> [    0.766350]  [<c1fa7dec>] kernel_init_freeable+0xd6/0x153
> [    0.766350]  [<c1fa7dec>] kernel_init_freeable+0xd6/0x153
> [    0.767370]  [<c1fa7dec>] ? kernel_init_freeable+0xd6/0x153
> [    0.767370]  [<c1fa7dec>] ? kernel_init_freeable+0xd6/0x153
> [    0.768426]  [<c1aab7a0>] kernel_init+0x10/0xe0
> [    0.768426]  [<c1aab7a0>] kernel_init+0x10/0xe0
> [    0.769296]  [<c1061445>] ? schedule_tail+0x25/0x70
> [    0.769296]  [<c1061445>] ? schedule_tail+0x25/0x70
> [    0.770424]  [<c1abe060>] ret_from_kernel_thread+0x20/0x30
> [    0.770424]  [<c1abe060>] ret_from_kernel_thread+0x20/0x30
> [    0.771456]  [<c1aab790>] ? rest_init+0xb0/0xb0
> [    0.771456]  [<c1aab790>] ? rest_init+0xb0/0xb0
> [    0.772362] ---[ end trace e098947396137dbd ]---
> [    0.772362] ---[ end trace e098947396137dbd ]---

Well the self test fails like it should on hardware without IMR support :)

Curious what the QEMU setup is like ?

To get to the self test code we need to get past this

static const struct x86_cpu_id imr_ids[] __initconst = {
         { X86_VENDOR_INTEL, 5, 9 },     /* Intel Quark SoC X1000. */
         {}
};
MODULE_DEVICE_TABLE(x86cpu, imr_ids);

if (!x86_match_cpu(imr_ids) || !iosf_mbi_available())
     return -ENODEV;

Looks to me like a version of QEMU that reports iosf_mbi available, 
cpuid 5/9 but lacks full IMR support ?

How do I replicate this setup ?

WARNING: multiple messages have this Message-ID (diff)
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Huang Ying <ying.huang@intel.com>
Cc: 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: Mon, 30 Mar 2015 09:15:06 +0100	[thread overview]
Message-ID: <5519060A.3080909@nexus-software.ie> (raw)
In-Reply-To: <1427696929.17170.82.camel@intel.com>


> [    0.752570]  [<c1ab0845>] dump_stack+0x16/0x18
> [    0.752570]  [<c1ab0845>] dump_stack+0x16/0x18
> [    0.753420]  [<c103bb27>] warn_slowpath_common+0x87/0xc0
> [    0.753420]  [<c103bb27>] warn_slowpath_common+0x87/0xc0
> [    0.754429]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.754429]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.755384]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.755384]  [<c1038674>] ? imr_add_range+0x2b4/0x370
> [    0.756335]  [<c103bbc3>] warn_slowpath_fmt+0x33/0x40
> [    0.756335]  [<c103bbc3>] warn_slowpath_fmt+0x33/0x40
> [    0.757293]  [<c1038674>] imr_add_range+0x2b4/0x370
> [    0.757293]  [<c1038674>] imr_add_range+0x2b4/0x370
> [    0.758219]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.758219]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.759200]  [<c103209a>] ? __phys_addr+0x3a/0x90
> [    0.759200]  [<c103209a>] ? __phys_addr+0x3a/0x90
> [    0.760090]  [<c106e4de>] ? debug_check_no_locks_freed+0x9e/0x160
> [    0.760090]  [<c106e4de>] ? debug_check_no_locks_freed+0x9e/0x160
> [    0.761361]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.761361]  [<c103057c>] ? slow_virt_to_phys+0x2c/0x90
> [    0.762419]  [<c1fb836a>] imr_self_test_init+0x40/0x1d9
> [    0.762419]  [<c1fb836a>] imr_self_test_init+0x40/0x1d9
> [    0.763439]  [<c1fb832a>] ? imr_self_test_result+0x4e/0x4e
> [    0.763439]  [<c1fb832a>] ? imr_self_test_result+0x4e/0x4e
> [    0.764477]  [<c1fa7d03>] do_one_initcall+0x180/0x193
> [    0.764477]  [<c1fa7d03>] do_one_initcall+0x180/0x193
> [    0.765443]  [<c10568bb>] ? parse_args+0x25b/0x530
> [    0.765443]  [<c10568bb>] ? parse_args+0x25b/0x530
> [    0.766350]  [<c1fa7dec>] kernel_init_freeable+0xd6/0x153
> [    0.766350]  [<c1fa7dec>] kernel_init_freeable+0xd6/0x153
> [    0.767370]  [<c1fa7dec>] ? kernel_init_freeable+0xd6/0x153
> [    0.767370]  [<c1fa7dec>] ? kernel_init_freeable+0xd6/0x153
> [    0.768426]  [<c1aab7a0>] kernel_init+0x10/0xe0
> [    0.768426]  [<c1aab7a0>] kernel_init+0x10/0xe0
> [    0.769296]  [<c1061445>] ? schedule_tail+0x25/0x70
> [    0.769296]  [<c1061445>] ? schedule_tail+0x25/0x70
> [    0.770424]  [<c1abe060>] ret_from_kernel_thread+0x20/0x30
> [    0.770424]  [<c1abe060>] ret_from_kernel_thread+0x20/0x30
> [    0.771456]  [<c1aab790>] ? rest_init+0xb0/0xb0
> [    0.771456]  [<c1aab790>] ? rest_init+0xb0/0xb0
> [    0.772362] ---[ end trace e098947396137dbd ]---
> [    0.772362] ---[ end trace e098947396137dbd ]---

Well the self test fails like it should on hardware without IMR support :)

Curious what the QEMU setup is like ?

To get to the self test code we need to get past this

static const struct x86_cpu_id imr_ids[] __initconst = {
         { X86_VENDOR_INTEL, 5, 9 },     /* Intel Quark SoC X1000. */
         {}
};
MODULE_DEVICE_TABLE(x86cpu, imr_ids);

if (!x86_match_cpu(imr_ids) || !iosf_mbi_available())
     return -ENODEV;

Looks to me like a version of QEMU that reports iosf_mbi available, 
cpuid 5/9 but lacks full IMR support ?

How do I replicate this setup ?

  reply	other threads:[~2015-03-30  8:15 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 [this message]
2015-03-30  8:15   ` 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
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=5519060A.3080909@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.