public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: x86@kernel.org, yinghai@kernel.org, macro@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option
Date: Wed, 14 Oct 2009 19:56:16 +0200	[thread overview]
Message-ID: <20091014175616.GA3403@elte.hu> (raw)
In-Reply-To: <20091014150904.GA5259@lenovo>


btw., i'm getting this warning on a test-box:

[    0.290000] Initializing cgroup subsys net_cls
[    0.300000] ------------[ cut here ]------------
[    0.300000] WARNING: at arch/x86/kernel/apic/apic_noop.c:42 warn_apic_enabled+0x5d/0x80()
[    0.310000] Hardware name: System Product Name
[    0.320000] APIC: Called for NOOP operation with apic enabled
[    0.320000] Modules linked in:
[    0.330000] Pid: 0, comm: swapper Not tainted 2.6.32-rc4-tip-01511-g59b4c9d-dirty #1741
[    0.330000] Call Trace:
[    0.340000]  [<79061fa5>] warn_slowpath_common+0x65/0xa0
[    0.340000]  [<7903d84d>] ? warn_apic_enabled+0x5d/0x80
[    0.350000]  [<7906203f>] warn_slowpath_fmt+0x2f/0x50
[    0.350000]  [<7903d84d>] warn_apic_enabled+0x5d/0x80
[    0.360000]  [<7903da96>] noop_default_phys_pkg_id+0x16/0x30
[    0.360000]  [<79af1514>] generic_identify+0xa3/0x176
[    0.370000]  [<79af165f>] identify_cpu+0x78/0x1fd
[    0.370000]  [<792c8d7d>] ? __init_rwsem+0x4d/0x70
[    0.380000]  [<79abcb54>] identify_boot_cpu+0xd/0x1e
[    0.380000]  [<79abcdae>] check_bugs+0x16/0xe5
[    0.390000]  [<79ab6b39>] start_kernel+0x31d/0x342
[    0.390000]  [<79ab60aa>] i386_start_kernel+0xaa/0xc2
[    0.400000] ---[ end trace a7919e7f17c0a725 ]---
[    0.400000] Checking 'hlt' instruction... OK.
[    0.440000] SMP alternatives: switching to UP code
[    0.450000] debug: unmapping init memory 79c7a000..79c80000

noop_default_phys_pkg_id() should return 0 i guess, and not generate a 
warning?

	Ingo

  parent reply	other threads:[~2009-10-14 17:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 20:07 [patch 0/3] x86 apic series Cyrill Gorcunov
2009-10-13 20:07 ` [patch 1/3] x86,apic: introduce NOOP apic driver Cyrill Gorcunov
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Introduce the " tip-bot for Cyrill Gorcunov
2009-10-13 20:07 ` [patch 2/3] x86,apic -- use apic noop driver Cyrill Gorcunov
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Use " tip-bot for Cyrill Gorcunov
2009-10-13 20:07 ` [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option Cyrill Gorcunov
2009-10-14  7:12   ` Ingo Molnar
2009-10-14  7:51     ` Cyrill Gorcunov
2009-10-14 15:09     ` Cyrill Gorcunov
2009-10-14 15:40       ` [tip:x86/apic] x86, apic: Explain show_lapic= in kernel parameters list tip-bot for Cyrill Gorcunov
2009-10-14 17:56       ` Ingo Molnar [this message]
2009-10-14 18:00         ` [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option Cyrill Gorcunov
2009-10-14 18:20         ` Cyrill Gorcunov
2009-10-14 20:29         ` Cyrill Gorcunov
2009-10-15 14:27           ` Cyrill Gorcunov
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Limit apic dumping, introduce new show_lapic= " tip-bot for Cyrill Gorcunov

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=20091014175616.GA3403@elte.hu \
    --to=mingo@elte.hu \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox