From: Vegard Nossum <vegard.nossum@gmail.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: WARNING: at arch/x86/kernel/apic/apic.c:249 native_apic_write_dummy
Date: Wed, 17 Jun 2009 18:33:31 +0200 [thread overview]
Message-ID: <19f34abd0906170933m6be38a4cv2e4f49c3b78d71c4@mail.gmail.com> (raw)
In-Reply-To: <20090617155337.GA10822@lenovo>
2009/6/17 Cyrill Gorcunov <gorcunov@gmail.com>:
> Vegard, could you test the patch?
>
> -- Cyrill
> ---
>
> If we have apic disabled we don't even switch to APIC mode and do not
> calling for connect_bsp_APIC. Though on SMP compiled kernel the
> native_machine_shutdown does try to write the apic register anyway.
> Fix it with explicit check if we really should touch apic registers.
>
> Reported-by: Vegard Nossum <vegard.nossum@gmail.com>
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> ---
> arch/x86/kernel/apic/io_apic.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.git/arch/x86/kernel/apic/io_apic.c
> =====================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/apic/io_apic.c
> +++ linux-2.6.git/arch/x86/kernel/apic/io_apic.c
> @@ -2003,7 +2003,9 @@ void disable_IO_APIC(void)
> /*
> * Use virtual wire A mode when interrupt remapping is enabled.
> */
> - disconnect_bsp_APIC(!intr_remapping_enabled && ioapic_i8259.pin != -1);
> + if (cpu_has_apic)
> + disconnect_bsp_APIC(!intr_remapping_enabled &&
> + ioapic_i8259.pin != -1);
> }
>
> #ifdef CONFIG_X86_32
>
Seems to work here:
[ 317.596743] ACPI: Preparing to enter system sleep state S5
[ 317.633421] Disabling non-boot CPUs ...
[ 317.637493] Power down.
[ 317.638305] acpi_power_off called
and no warning.
Thanks!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2009-06-17 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 15:11 Vegard Nossum
2009-06-17 15:14 ` Cyrill Gorcunov
2009-06-17 15:46 ` Vegard Nossum
2009-06-17 15:53 ` Cyrill Gorcunov
2009-06-17 16:33 ` Vegard Nossum [this message]
2009-06-17 16:37 ` 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=19f34abd0906170933m6be38a4cv2e4f49c3b78d71c4@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®