Bug 1970602

Summary: [abrt] efi_memattr_apply_permissions: WARNING: CPU: 0 PID: 0 at kernel/iomem.c:81 memremap+0x19a/0x1d0
Product: [Fedora] Fedora Reporter: Antonio Evers <antonioev>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: acaringi, adscvr, airlied, alciregi, artem.python, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2daf909ce60b372deb2d403c9ba3b476aabdce2a
Whiteboard: abrt_hash:c54e96282af28d3b109d5eabe2269e3d0e7f3fd0;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:37:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Antonio Evers 2021-06-10 18:47:29 UTC 
Description of problem:
Not sure the Laptop was starting and the problem reporting tool just popup.

Additional info:
reporter:       libreport-2.15.2
WARNING: CPU: 0 PID: 0 at kernel/iomem.c:81 memremap+0x19a/0x1d0
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.12.9-300.fc34.x86_64 #1
Hardware name: Dell Inc. Latitude 5480/0NDFXD, BIOS 1.17.1 01/07/2020
RIP: 0010:memremap+0x19a/0x1d0
Code: d6 fe ff ff 80 3d 9d d0 aa 01 00 0f 85 c7 fe ff ff 4c 89 e2 48 89 e6 48 c7 c7 48 93 3c 83 c6 05 83 d0 aa 01 01 e8 b3 33 92 00 <0f> 0b e9 a7 fe ff ff 48 89 da 4c 89 e6 48 89 ef e8 01 f9 e0 ff 84
RSP: 0000:ffffffff83a03de0 EFLAGS: 00010282
RAX: 0000000000000045 RBX: 0000000000000001 RCX: ffffffff83b15ee8
RDX: c0000000ffffdfff RSI: 00000000ffffdfff RDI: ffffffff8452ec6c
RBP: ffffffffff200190 R08: 0000000000000000 R09: ffffffff83a03c10
R10: ffffffff83a03c08 R11: ffffffff83b45f28 R12: 0000000058514010
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000004
FS:  0000000000000000(0000) GS:ffff896361400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8963717ff000 CR3: 0000000047a10001 CR4: 00000000000606b0
Call Trace:
 efi_memattr_apply_permissions+0x6f/0x298
 ? __map_region+0x8f/0x8f
 ? __efi_memmap_init+0x7a/0xd4
 ? efi_free_boot_services+0x1fa/0x219
 efi_enter_virtual_mode+0x406/0x426
 start_kernel+0x7b7/0x83a
 ? apply_microcode_early.cold+0x8/0x1d
 secondary_startup_64_no_verify+0xc2/0xcb
Comment 1 Antonio Evers 2021-06-10 18:47:34 UTC 
Created attachment 1789974 [details]
File: dmesg
Comment 2 Ben Cotton 2022-05-12 15:46:13 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 3 Ben Cotton 2022-06-07 22:37:46 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.