From: Jiri Slaby <jslaby@suse.cz>
To: marc.zyngier@arm.com, Thomas Gleixner <tglx@linutronix.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: andre.przywara@arm.com
Subject: irqdomain patch prevents booting qemu
Date: Fri, 3 Feb 2017 12:49:01 +0100 [thread overview]
Message-ID: <922d42de-635a-ffd7-b6bd-2e4edf7d4307@suse.cz> (raw)
Hi,
with this -next commit:
commit 08d85f3ea99f1eeafc4e8507936190e86a16ee8c
Author: Marc Zyngier <marc.zyngier@arm.com>
Date: Tue Jan 17 16:00:48 2017 +0000
irqdomain: Avoid activating interrupts more than once
I can no longer boot qemu machine. It stops booting at:
[ 0.477566] x2apic enabled
[ 0.478154] Switched APIC routing to physical x2apic.
[ 0.479405] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
It loops in:
#0 calibrate_APIC_clock () at arch/x86/kernel/apic/apic.c:757
#1 setup_boot_APIC_clock () at arch/x86/kernel/apic/apic.c:880
#2 0xffffffff81f7bef2 in apic_bsp_setup (upmode=<optimized out>)
at arch/x86/kernel/apic/apic.c:2300
#3 0xffffffff81f79c84 in native_smp_prepare_cpus (max_cpus=<optimized out>)
at arch/x86/kernel/smpboot.c:1339
#4 0xffffffff81f6801d in smp_prepare_cpus (max_cpus=<optimized out>)
at ./arch/x86/include/asm/smp.h:85
#5 kernel_init_freeable () at init/main.c:1020
#6 0xffffffff8192372e in kernel_init (unused=<optimized out>)
at init/main.c:956
#7 0xffffffff8192ac5c in ret_from_fork () at arch/x86/entry/entry_64.S:430
which is:
757 while (lapic_cal_loops <= LAPIC_CAL_LOOPS)
758 cpu_relax();
lapic_cal_loops is not incrementing, so it seems that interrupts are not
coming.
Reverting the commit makes the machine boot again.
thanks,
--
js
suse labs
next reply other threads:[~2017-02-03 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:49 Jiri Slaby [this message]
2017-02-03 11:57 ` Marc Zyngier
2017-02-03 12:11 ` Jiri Slaby
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=922d42de-635a-ffd7-b6bd-2e4edf7d4307@suse.cz \
--to=jslaby@suse.cz \
--cc=andre.przywara@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/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®