From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Simon Holm Thøgersen" <odie@cs.aau.dk>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>
Subject: Re: apic: native_apic_write_dummy warning
Date: Sun, 14 Jun 2009 23:40:17 +0400 [thread overview]
Message-ID: <20090614194017.GA24604@lenovo> (raw)
In-Reply-To: <20090614192220.GB4851@lenovo>
[Cyrill Gorcunov - Sun, Jun 14, 2009 at 11:22:20PM +0400]
| [Simon Holm Thøgersen - Sun, Jun 14, 2009 at 09:05:50PM +0200]
| | Hi Cyrill
| |
| | I guess you want to know about these warnings, so here you go
| |
| | WARNING: at arch/x86/kernel/apic/apic.c:249 native_apic_write_dummy+0x32/0x3e()
| | Hardware name:
| | Modules linked in:
| | Pid: 0, comm: swapper Not tainted 2.6.30-debug-03392-g44b7532 #17
| | Call Trace:
| | [<c0126bed>] warn_slowpath_common+0x65/0x95
| | [ 0.006956] [<c0126c2f>] warn_slowpath_null+0x12/0x15
| | [ 0.007031] [<c0112269>] native_apic_write_dummy+0x32/0x3e
| | [ 0.007109] [<c010e027>] intel_init_thermal+0xd3/0x178
| | [ 0.007185] [<c01168ce>] ? native_read_msr_safe+0x9/0x16
| | [ 0.007263] [<c0194197>] ? __kmalloc+0x117/0x123
| | [ 0.007338] [<c010deb2>] mce_intel_feature_init+0x10/0x50
| | [ 0.007416] [<c05ee0a4>] mcheck_init+0x1d5/0x263
| | [ 0.007492] [<c05eda0a>] identify_cpu+0x369/0x378
| | [ 0.007569] [<c03432ac>] ? _spin_unlock+0x3d/0x49
| | [ 0.007644] [<c01cc5ff>] ? proc_register+0x150/0x161
| | [ 0.007721] [<c05d2a15>] identify_boot_cpu+0xd/0x23
| | [ 0.007796] [<c05d2a67>] check_bugs+0xb/0xf1
| | [ 0.007872] [<c05cc966>] start_kernel+0x293/0x2a7
| | [ 0.008011] [<c05cc30b>] i386_start_kernel+0x65/0x6a
| |
| |
| | Simon Holm Thøgersen
|
| Hi Simon, thanks a lot for report! Will take a look.
|
| -- Cyrill
Neither thermal interrupts nor mce will be functional if apic
is not properly set up (even having kernel compiled that way
it support both). So you may try to pass "lapic" boot option
and check if we're lucky in attempt to enable apic via force
push. Anyway this warn show that the code is to be fixed
(and native_apic_write_dummy done its work great catching
useless apic->write operation). I'll handle it but a bit later.
Andi CC'ed since he is involved in MCE handling just for the
record.
-- Cyrill
next prev parent reply other threads:[~2009-06-14 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 19:05 apic: native_apic_write_dummy warning Simon Holm Thøgersen
2009-06-14 19:22 ` Cyrill Gorcunov
2009-06-14 19:40 ` Cyrill Gorcunov [this message]
2009-06-14 20:06 ` Cyrill Gorcunov
2009-06-14 21:50 ` Simon Holm Thøgersen
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=20090614194017.GA24604@lenovo \
--to=gorcunov@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=odie@cs.aau.dk \
/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