Bug 1396653

Summary: [abrt] WARNING: CPU: 0 PID: 1 at mm/early_ioremap.c:91 check_early_ioremap_leak+0x3b/0x42
Product: [Fedora] Fedora Reporter: Szymon <szymonbrzezinski>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA 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
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7a14ad4629320f721dc32c1d3e0708cf80253f81
Whiteboard: abrt_hash:f31e49f4b7c1e1873f14d32fd81a588f8b99a9b7;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:25:12 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 Szymon 2016-11-18 20:40:09 UTC 
Description of problem:
Right after boot

Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 1 at mm/early_ioremap.c:91 check_early_ioremap_leak+0x3b/0x42
Debug warning: early ioremap leak of 1 areas detected.
please boot with early_ioremap_debug and report the dmesg.
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.6-201.fc24.x86_64 #1
Hardware name: LENOVO 20132/Product Name, BIOS 5DCN40WW(V2.07) 10/10/2012
 0000000000000286 00000000a6298499 ffff96b8b5a0bd90 ffffffff963e5ebd
 ffff96b8b5a0bde0 0000000000000000 ffff96b8b5a0bdd0 ffffffff960a0e8b
 0000005bb6406238 0000000000000000 ffffffff96fb7e9a ffffffff970db340
Call Trace:
 [<ffffffff963e5ebd>] dump_stack+0x63/0x86
 [<ffffffff960a0e8b>] __warn+0xcb/0xf0
 [<ffffffff96fb7e9a>] ? early_ioremap_debug_setup+0x12/0x12
 [<ffffffff96f7f8cd>] ? set_debug_rodata+0x12/0x12
 [<ffffffff960a0f0f>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffff96fb717a>] ? setup_transparent_hugepage+0x99/0x99
 [<ffffffff96f7f8cd>] ? set_debug_rodata+0x12/0x12
 [<ffffffff96fb7ed5>] check_early_ioremap_leak+0x3b/0x42
 [<ffffffff96002190>] do_one_initcall+0x50/0x180
 [<ffffffff96f7f8cd>] ? set_debug_rodata+0x12/0x12
 [<ffffffff96f801a0>] kernel_init_freeable+0x194/0x230
 [<ffffffff967f4ede>] kernel_init+0xe/0x100
 [<ffffffff9680277f>] ret_from_fork+0x1f/0x40
 [<ffffffff967f4ed0>] ? rest_init+0x80/0x80
Comment 1 Szymon 2016-11-18 20:40:22 UTC 
Created attachment 1222006 [details]
File: dmesg
Comment 2 Justin M. Forbes 2017-04-11 15:00:34 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 25 has now been rebased to 4.10.9-100.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 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 Justin M. Forbes 2017-04-28 17:25:12 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.