From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: Linux dom0 hangs on boot with Xen 4.22 and Heads firmware
Date: Fri, 19 Jun 2026 16:38:03 +0200 [thread overview]
Message-ID: <ajVUS5F9G4Jse20i@mail-itl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Hi,
After updating Xen to 4.22-rc2 on a system with Heads firmware, dom0
doesn't start anymore. It worked fine with Xen 4.19.
The last messages on console are:
[ 1.495140] installing Xen timer for CPU 2
[ 1.496149] installing Xen timer for CPU 4
[ 1.496587] installing Xen timer for CPU 5
[ 1.496809] installing Xen timer for CPU 7
[ 0.008235] [Firmware Bug]: CPU 2: APIC ID mismatch. CPUID: 0x0002 APIC: 0x0028
[ 0.008235] [Firmware Bug]: CPU 2: APIC ID mismatch. Firmware: 0x0011 APIC: 0x0028
[ 1.497055] cpu 2 spinlock event irq 200
[ 0.008235] [Firmware Bug]: CPU 4: APIC ID mismatch. CPUID: 0x0004 APIC: 0x0000
[ 0.008235] [Firmware Bug]: CPU 4: APIC ID mismatch. Firmware: 0x0019 APIC: 0x0000
[ 1.497074] cpu 4 spinlock event irq 201
[ 0.008235] [Firmware Bug]: CPU 5: APIC ID mismatch. CPUID: 0x0005 APIC: 0x0002
[ 0.008235] [Firmware Bug]: CPU 5: APIC ID mismatch. Firmware: 0x0021 APIC: 0x0002
[ 1.497074] cpu 5 spinlock event irq 202
[ 0.008235] [Firmware Bug]: CPU 7: APIC I
Full console log (containing both successful boot of Xen 4.19, and then
reboot into 4.22):
https://openqa.qubes-os.org/tests/184780/logfile?filename=serial0.txt
It doesn't reach loading graphics driver in dom0, so I don't have
anything interesting on VGA (the last output is about the kexec call
done by Heads). But at least I have a serial console.
This happens both on older Thinkpad t430 (Ivy Bridge), and newer Novacustom V54 (ADL).
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-06-19 14:38 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=ajVUS5F9G4Jse20i@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.