From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218980] [VM boot] Guest Kernel hit BUG: kernel NULL pointer dereference, address: 0000000000000010 and WARNING: CPU: 0 PID: 218 at arch/x86/kernel/fpu/core.c:57 x86_task_fpu+0x17/0x20
Date: Sun, 30 Jun 2024 22:21:14 +0000 [thread overview]
Message-ID: <bug-218980-28872-nBCD6tPERO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218980-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218980
--- Comment #5 from Luis Chamberlain (mcgrof@kernel.org) ---
On Mon, Jun 24, 2024 at 06:43:54AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218980
>
> Bug ID: 218980
> Summary: [VM boot] Guest Kernel hit BUG: kernel NULL pointer
> dereference, address: 0000000000000010 and WARNING:
> CPU: 0 PID: 218 at arch/x86/kernel/fpu/core.c:57
> x86_task_fpu+0x17/0x20
> Product: Virtualization
> Version: unspecified
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: kvm
> Assignee: virtualization_kvm@kernel-bugs.osdl.org
> Reporter: hongyu.ning@intel.com
> Regression: No
>
> Created attachment 306485
> --> https://bugzilla.kernel.org/attachment.cgi?id=306485&action=edit
> WARNING/BUG and Call Trace info in dmesg
>
> in an regular linux-next guest kernel regression test setup, recently hit
> following BUG and WARNING, likely related to x86/fpu.
> [ 1.962383] ? fpstate_free+0x5/0x30
Yeah we run into the same thing on *all* boots on linux-next on kdevops
as well, Cc'ing kdevops list so folks are aware linux-next is broken
right now.
[ 16.785349] BUG: kernel NULL pointer dereference, address:
0000000000000010
[ 16.785353] #PF: supervisor read access in kernel mode
[ OK ] Found device[ 16.785354] #PF: error_code(0x0000) -
not-present page
dev-disk-by\x2dlabel-…evice - QEMU NVMe Ctrl sparsefiles.
[ 16.785356] PGD 0 P4D 0
[ 16.785358] Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 16.785361] CPU: 1 UID: 0 PID: 528 Comm: modprobe Tainted: G
W 6.10.0-rc5-next-20240628+ #8
[ 16.785365] Tainted: [W]=WARN
[ 16.785366] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
1.16.3-debian-1.16.3-2 04/01/2014
[ 16.785367] RIP: 0010:fpstate_free+0x5/0x30
[ 16.785373] Code: 41 5c 41 5d 41 5e c3 cc cc cc cc 66 2e 0f 1f 84 00
00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00
00 <48> 8b 47 10 48 85 c0 74 11 48 83 c7 40 48
39 f8 74 08 48 89 c7 e9
[ 16.785374] RSP: 0000:ffffb4dd80673e48 EFLAGS: 00010246
[ 16.785376] RAX: 0000000000000000 RBX: ffff8eca5fdd0000 RCX:
00000000801c0012
[ 16.785378] RDX: ffff8eca54bef500 RSI: ffffffff8aa9b92d RDI:
0000000000000000
[ 16.785379] RBP: ffff8ecabbc72840 R08: ffff8eca54bed100 R09:
00000000801c0012
[ 16.785380] R10: 00000000801c0012 R11: 0000000000000001 R12:
ffff8eca605dc800
[ 16.785381] R13: 0000000000030bc8 R14: ffff8ecabbc728b8 R15:
0000000000000004
[ 16.785382] FS: 00007f26f73a35c0(0000) GS:ffff8ecabbc40000(0000)
knlGS:0000000000000000
[ 16.785383] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 16.785385] CR2: 0000000000000010 CR3: 00000001175b6006 CR4:
0000000000770ef0
[ 16.785389] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 16.785390] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7:
0000000000000400
[ 16.785391] PKRU: 55555554
[ 16.785392] Call Trace:
[ 16.785394] <TASK>
[ 16.785396] ? __die+0x1f/0x60
[ 16.785401] ? page_fault_oops+0x158/0x460
[ 16.785406] ? x86_task_fpu+0x17/0x20
[ 16.785410] ? do_user_addr_fault+0x63/0x6c0
[ 16.785413] ? exc_page_fault+0x79/0x190
[ 16.785417] ? asm_exc_page_fault+0x22/0x30
[ 16.785420] ? free_task+0x2d/0x70
[ 16.785424] ? fpstate_free+0x5/0x30
[ 16.785427] ? arch_release_task_struct+0x27/0x30
[ 16.785429] free_task+0x35/0x70
[ 16.785432] rcu_core+0x499/0x7d0
[ 16.785436] ? rcu_core+0x434/0x7d0
[ 16.785440] handle_softirqs+0xf9/0x300
[ 16.785444] __irq_exit_rcu+0x6e/0xc0
[ 16.785446] sysvec_apic_timer_interrupt+0x51/0xc0
[ 16.785450] asm_sysvec_apic_timer_interrupt+0x16/0x20
[ 16.785452] RIP: 0033:0x7f26f74d0858
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-06-30 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 6:43 [Bug 218980] New: [VM boot] Guest Kernel hit BUG: kernel NULL pointer dereference, address: 0000000000000010 and WARNING: CPU: 0 PID: 218 at arch/x86/kernel/fpu/core.c:57 x86_task_fpu+0x17/0x20 bugzilla-daemon
2024-06-24 6:44 ` [Bug 218980] " bugzilla-daemon
2024-06-24 6:44 ` bugzilla-daemon
2024-06-24 7:16 ` bugzilla-daemon
2024-06-24 11:08 ` bugzilla-daemon
2024-06-27 3:41 ` bugzilla-daemon
2024-06-30 22:21 ` [Bug 218980] New: " Luis Chamberlain
2024-06-30 22:47 ` Luis Chamberlain
2024-07-08 21:56 ` Luis Chamberlain
2024-06-30 22:21 ` bugzilla-daemon [this message]
2024-06-30 22:48 ` [Bug 218980] " bugzilla-daemon
2024-07-08 21:56 ` bugzilla-daemon
2024-07-15 1:40 ` bugzilla-daemon
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=bug-218980-28872-nBCD6tPERO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@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 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.