Bug 1372233 - [abrt] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:590 fpu__init_system_xstate+0x4d0/0x877
Summary: [abrt] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:590 fpu__init_s...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:50b237afbfc83a9d32d1e8a5bdb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 08:26 UTC by Timo Klerx
Modified: 2020-05-26 09:45 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 23:04:28 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (41.84 KB, text/plain)
2016-09-01 08:26 UTC, Timo Klerx
no flags Details

Description Timo Klerx 2016-09-01 08:26:35 UTC
Description of problem:
Running F25 in VirtualBox
Recently installed VirtualBox Guest Addons

Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:590 fpu__init_system_xstate+0x4d0/0x877
XSAVE consistency problem, dumping leaves
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.8.0-0.rc2.git3.1.fc25.x86_64 #1
 0000000000000086 ea8840f3ea883fad ffffffffa4e03d80 ffffffffa4467eb3
 ffffffffa4e03dd0 0000000000000000 ffffffffa4e03dc0 ffffffffa40ae6db
 0000024e00000002 000000000000000a 0000000000000340 0000000000000440
Call Trace:
 [<ffffffffa4467eb3>] dump_stack+0x86/0xc3
 [<ffffffffa40ae6db>] __warn+0xcb/0xf0
 [<ffffffffa40ae75f>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffffa40a980b>] ? xfeature_size+0x5a/0x78
 [<ffffffffa51d7487>] fpu__init_system_xstate+0x4d0/0x877
 [<ffffffffa44a37fa>] ? msr_clear_bit+0x3a/0xa0
 [<ffffffffa51d6bc6>] fpu__init_system+0x1d1/0x27d
 [<ffffffffa51d7f0f>] early_cpu_init+0xf7/0xf9
 [<ffffffffa51d2f42>] setup_arch+0xba/0xcf0
 [<ffffffffa41f5c31>] ? printk+0x57/0x73
 [<ffffffffa51c7120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffffa51c7c48>] start_kernel+0xbc/0x4af
 [<ffffffffa51c7120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffffa51c72ca>] x86_64_start_reservations+0x24/0x26
 [<ffffffffa51c7419>] x86_64_start_kernel+0x14d/0x170

Potential duplicate: bug 1369575

Comment 1 Timo Klerx 2016-09-01 08:26:47 UTC
Created attachment 1196621 [details]
File: dmesg

Comment 2 Laura Abbott 2017-01-17 01:14:31 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Laura Abbott 2017-02-23 23:04:28 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.