From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Anthony PERARD <anthony.perard@vates.tech>
Cc: xen-devel@lists.xenproject.org,
"Ross Lagerwall" <ross.lagerwall@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>
Subject: Re: Assertion '!is_idle_vcpu(v)' failed after 'Remove fully_eager_fpu' commit on EFI
Date: Fri, 12 Jun 2026 16:11:28 +0200 [thread overview]
Message-ID: <aiwTkDUP6rDPbV6R@mail-itl> (raw)
In-Reply-To: <1781272430.8631fc262581453bbf619ec5b2062170.19ebc1c488b000701b@vates.tech>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
On Fri, Jun 12, 2026 at 03:53:49PM +0200, Anthony PERARD wrote:
> Hi,
>
> Since commit dba44e051209 ("x86: Remove fully_eager_fpu"), I can't boot
> a machine and get assertion '!is_idle_vcpu(v)' failed instead. It's
> netbooted and EFI.
>
> Xen call trace:
> [<ffff82d04033da2c>] R vcpu_save_fpu+0x65/0xdc
> [<ffff82d04029c5c4>] S efi_rs_enter+0x37/0x16a
> [<ffff82d04029c7e3>] F efi_get_time+0x19/0xb2
> [<ffff82d04047cbf0>] F init_xen_time+0x1e3/0x2b4
> [<ffff82d040477a49>] F __start_xen+0x1d71/0x24b8
> [<ffff82d0402043e7>] F __high_start+0xb7/0xc0
>
> Assertion '!is_idle_vcpu(v)' failed at arch/x86/i387.c:195
>
> A few more lines from Xen:
> CPU Vendor: Intel, Family 6 (0x6), Model 86 (0x56), Stepping 3 (raw 00050663)
> Bootloader: GRUB 2.06
> [...]
> Enabling APIC mode. Using 2 I/O APICs
> ENABLING IO-APIC IRQs
> -> Using old ACK method
> ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> TSC deadline timer enabled
> Assertion '!is_idle_vcpu(v)' failed at arch/x86/i387.c:195
>
> Commit this Xen is built from: 50936ea05660.
Interesting, the efi_get_time() way is nowadays a fallback if cmos one
isn't advertised. Can you try adding `cmos-rtc-probe`?
Anyway, surely it shouldn't crash... The commit you mentioned has "No
functional change intended", but well...
> full logs at:
> https://paste.vates.tech/?bd8a9a0955798a97#A1DU2efwUt7bbHQUxdo9UXGcsJ2XPNJNZHPz87LqLtcF
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-12 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 13:53 Assertion '!is_idle_vcpu(v)' failed after 'Remove fully_eager_fpu' commit on EFI Anthony PERARD
2026-06-12 14:11 ` Marek Marczykowski-Górecki [this message]
2026-06-12 14:18 ` Andrew Cooper
2026-06-12 14:20 ` Jan Beulich
2026-06-12 14:32 ` Andrew Cooper
2026-06-12 14:45 ` Jan Beulich
2026-06-12 14:54 ` Andrew Cooper
2026-06-12 15:17 ` Anthony PERARD
2026-06-15 9:02 ` Roger Pau Monné
2026-06-15 14:39 ` Anthony PERARD
2026-06-15 17:02 ` Andrew Cooper
2026-06-16 6:16 ` Jan Beulich
2026-06-16 7:07 ` Roger Pau Monné
2026-06-12 15:10 ` Anthony PERARD
2026-06-12 14:17 ` Jan Beulich
2026-06-12 15:41 ` [PATCH] x86/efi: Skip FPU save/restore for idle vCPU in EFI, runtime path Bernhard Kaindl
2026-06-12 16:00 ` Anthony PERARD
2026-06-15 6:52 ` Jan Beulich
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=aiwTkDUP6rDPbV6R@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=ross.lagerwall@citrix.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.