Fedora Account System
Red Hat Associate
Red Hat Customer
Additional info: reporter: libreport-2.9.3 WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60 Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 4.17.9-100.fc27.x86_64 #1 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Q87M-D2H, BIOS F4 06/14/2013 RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60 RSP: 0000:ffffffffb1203e00 EFLAGS: 00010086 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffb1252b48 RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046 RBP: ffffffffb10edb12 R08: 00000000000000d0 R09: 0000000000000004 R10: ffffffffb1203d88 R11: 0000000000000001 R12: ffffffffb1aa201c R13: ffffffffb1aa2064 R14: ffffffffb1203e80 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8d2d4e200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff8d285caa3000 CR3: 000000035c20a001 CR4: 00000000000606b0 Call Trace: dmar_validate_one_drhd+0xa2/0xd0 dmar_walk_remapping_entries+0xa2/0x1d0 detect_intel_iommu+0x64/0xed ? xen_swiotlb_init+0x4d0/0x4d0 pci_iommu_alloc+0x51/0x6c mem_init+0x16/0xb9 start_kernel+0x2cb/0x55b secondary_startup_64+0xa5/0xb0 Code: 59 19 00 bf 01 00 00 00 49 89 c4 e8 64 59 19 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 a0 61 12 b1 e8 a9 0b af ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 bb 5b 44 00 85 d2 7e 56 53 4c 8d Potential duplicate: bug 1562480
Created attachment 1471797 [details] File: dmesg
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 27 kernel bugs. Fedora 27 has now been rebased to 4.18.10-100.fc27. 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 28 or Fedora 29, and are still experiencing this issue, please change the version to Fedora 28 or 29. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
*** This bug has been marked as a duplicate of bug 1564895 ***