Bug 1369575

Summary: [abrt] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:533 fpu__init_system_xstate+0x435/0x742
Product: [Fedora] Fedora Reporter: Paul Lipps <paul.lipps>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, paul.lipps, timok
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f610b7df4b306a6b2e37d94a03b54e37088bbadd
Whiteboard: abrt_hash:50b237afbfc83a9d32d1e8a5bdb2eded84d74d08;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-03 14:26:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Paul Lipps 2016-08-23 19:58:04 UTC 
Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:533 fpu__init_system_xstate+0x435/0x742
XSAVE consistency problem, dumping leaves
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.6.4-301.fc24.x86_64 #1
 0000000000000086 bb4c7c52cc53cacd ffffffff81c03d90 ffffffff813dbcaf
 ffffffff81c03de0 0000000000000000 ffffffff81c03dd0 ffffffff810a742b
 00000215817e02e6 000000000000000a 0000000000000340 0000000000000100
Call Trace:
 [<ffffffff813dbcaf>] dump_stack+0x63/0x84
 [<ffffffff810a742b>] __warn+0xcb/0xf0
 [<ffffffff810a74af>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffff810a3294>] ? xfeature_size+0x5a/0x78
 [<ffffffff81d78a5b>] fpu__init_system_xstate+0x435/0x742
 [<ffffffff81d783a5>] fpu__init_system+0x1d7/0x283
 [<ffffffff81d79436>] early_cpu_init+0xf7/0xf9
 [<ffffffff81d74722>] setup_arch+0xba/0xd19
 [<ffffffff811b68cd>] ? printk+0x57/0x73
 [<ffffffff81d68120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffff81d68c65>] start_kernel+0xb2/0x474
 [<ffffffff81d68120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffff81d68346>] x86_64_start_reservations+0x2a/0x2c
 [<ffffffff81d68494>] x86_64_start_kernel+0x14c/0x16f
Comment 1 Paul Lipps 2016-08-23 19:58:13 UTC 
Created attachment 1193413 [details]
File: dmesg
Comment 2 Laura Abbott 2016-09-23 19:22:01 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 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  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 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.
Comment 3 Paul Lipps 2016-10-03 14:23:46 UTC 
This issue has not reoccurred with kernels >=4.7.4