From: Jeff DeFouw <jeffd@i2k.com>
To: linux-kernel@vger.kernel.org
Subject: WARNING at x86 smp_32.c:561 native_smp_call_function_mask()
Date: Thu, 14 Feb 2008 00:26:55 -0500 [thread overview]
Message-ID: <20080214052654.GA27184@blorp.plorb.com> (raw)
I noticed this WARNING fly by while booting 2.6.24.2. Everything seems
to be working though.
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium III (Katmai) stepping 02
Total of 2 processors activated (1805.98 BogoMIPS).
ExtINT not setup in hardware but reported by MP table
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask()
Pid: 1, comm: swapper Not tainted 2.6.24.2 #1
[<c010ed51>] native_smp_call_function_mask+0x171/0x180
[<c0103607>] common_interrupt+0x23/0x28
[<c010f950>] enable_NMI_through_LVT0+0x0/0x30
[<c010f950>] enable_NMI_through_LVT0+0x0/0x30
[<c010f08c>] smp_call_function+0x1c/0x20
[<c01210d1>] on_each_cpu+0x21/0x40
[<c0110fc0>] setup_nmi+0x30/0x50
[<c05ab3e5>] setup_IO_APIC+0xe15/0xf40
[<c01331a7>] atomic_notifier_call_chain+0x17/0x20
[<c02e756d>] notify_update+0x1d/0x30
[<c05a74be>] native_smp_prepare_cpus+0x55e/0xac0
[<c0116a29>] task_rq_lock+0x39/0x70
[<c0117ee6>] set_cpus_allowed+0x46/0xa0
[<c059f710>] kernel_init+0x0/0x300
[<c059f762>] kernel_init+0x52/0x300
[<c0118b17>] schedule_tail+0x17/0x60
[<c0102b42>] ret_from_fork+0x6/0x1c
[<c059f710>] kernel_init+0x0/0x300
[<c059f710>] kernel_init+0x0/0x300
[<c0103817>] kernel_thread_helper+0x7/0x10
=======================
APIC timer registered as dummy, due to nmi_watchdog=1!
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
560: /* Can deadlock when called with interrupts disabled */
561: WARN_ON(irqs_disabled());
--
Jeff DeFouw <jeffd@i2k.com>
reply other threads:[~2008-02-14 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080214052654.GA27184@blorp.plorb.com \
--to=jeffd@i2k.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®