Bug 1368223

Summary: [abrt] WARNING: CPU: 0 PID: 0 at arch/x86/mm/ioremap.c:104 __ioremap_caller+0x346/0x350
Product: [Fedora] Fedora Reporter: Oleg Pykhalov <go.wigust>
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, go.wigust, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: labbott: needinfo? (go.wigust)
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/673ded533a03c3cb2b51138caa320bf7f7488752
Whiteboard: abrt_hash:71bfdd0b0edee94b93802e714e9f4bc5ca22597c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-26 16:57:22 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 Oleg Pykhalov 2016-08-18 17:50:13 UTC 
Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 0 at arch/x86/mm/ioremap.c:104 __ioremap_caller+0x346/0x350
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.6.6-300.fc24.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H67M-GE/HT, BIOS P2.10 04/27/2012
 0000000000000286 847ab0c19581ff38 ffffffff81c03e10 ffffffff813dbf2f
 0000000000000000 0000000000000000 ffffffff81c03e50 ffffffff810a741b
 000000689581ff38 0000000000000001 ffffffff811b6412 09fd501800000001
Call Trace:
 [<ffffffff813dbf2f>] dump_stack+0x63/0x84
 [<ffffffff810a741b>] __warn+0xcb/0xf0
 [<ffffffff811b6412>] ? memremap+0xc2/0x180
 [<ffffffff810a754d>] warn_slowpath_null+0x1d/0x20
 [<ffffffff8106b096>] __ioremap_caller+0x346/0x350
 [<ffffffff817d72ec>] ? acpi_os_map_memory+0xe/0x10
 [<ffffffff8148e9a7>] ? acpi_tb_acquire_table+0x3e/0x6b
 [<ffffffff8106b134>] ioremap_cache+0x14/0x20
 [<ffffffff811b6412>] memremap+0xc2/0x180
 [<ffffffff81d89b64>] efi_bgrt_init+0xcf/0x1a8
 [<ffffffff81d88e9f>] efi_late_init+0x9/0xb
 [<ffffffff81d68ff7>] start_kernel+0x444/0x474
 [<ffffffff81d68120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffff81d68346>] x86_64_start_reservations+0x2a/0x2c
 [<ffffffff81d68494>] x86_64_start_kernel+0x14c/0x16f
Comment 1 Oleg Pykhalov 2016-08-18 17:50:23 UTC 
Created attachment 1191954 [details]
File: dmesg
Comment 2 Laura Abbott 2016-09-23 19:17:48 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 Laura Abbott 2016-10-26 16:57:22 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.