| Summary: | WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:830 warn_invalid_dmar+0x79/0x90() | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | g. artim <gartim> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | gansalmon, gartim, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-23 23:04:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
*********** 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. It was fc25, sorry typo. I used on the server edition and noted the dump in the syslog, but no problems I could find running the code. More of an fyi. I'll retest on that machine when 25 is released and reply, Gary I just noted the kernel say 24, but I did a sudo dnf system-upgrade download --refresh --releasever=25 sudo dnf system-upgrade reboot maybe the kernel update didnt happen. I'll try a retest. g. *********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. 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. *********** 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. Maybe I should just stop reporting these errors since I never seem to get much response. And just get "form response" when the release has matured. gary |
Description of problem: get trace dumps at bootup old acer laptop, firmware update, I doubt are available...fyi (see traceback below) Version-Release number of selected component (if applicable): Linux localhost.localdomain 4.5.0-302.fc24.x86_64 #1 SMP Wed Mar 30 15:41:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux How reproducible: boot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:830 warn_invalid_dmar+0x79/0x90() [ 0.000000] Your BIOS is broken; DMAR reported at address 0! BIOS vendor: INSYDE; Ver: V1.30; Product Version: V1.30 [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.5.0-302.fc24.x86_64 #1 [ 0.000000] Hardware name: Acer Aspire 4810T/Aspire 4810T, BIOS V1.30 09/29/2009 [ 0.000000] 0000000000000086 563611eb673d6065 ffffffff81c03d38 ffffffff813d3fdf [ 0.000000] ffffffff81c03d80 ffffffff81ab8bdc ffffffff81c03d70 ffffffff810a5de2 [ 0.000000] 0000000000000000 ffffffff81a98015 ffffffff8205d008 ffffffff8205d034 [ 0.000000] Call Trace: [ 0.000000] [<ffffffff813d3fdf>] dump_stack+0x63/0x84 [ 0.000000] [<ffffffff810a5de2>] warn_slowpath_common+0x82/0xc0 [ 0.000000] [<ffffffff810a5ef4>] warn_slowpath_fmt_taint+0x54/0x70 [ 0.000000] [<ffffffff81d9e498>] ? early_ioremap+0x9/0xb [ 0.000000] [<ffffffff81d7c83a>] ? __acpi_map_table+0x13/0x18 [ 0.000000] [<ffffffff814fb0f9>] warn_invalid_dmar+0x79/0x90 [ 0.000000] [<ffffffff817c3db9>] dmar_validate_one_drhd+0x99/0xc0 [ 0.000000] [<ffffffff814fb27a>] dmar_walk_remapping_entries+0x8a/0x1a0 [ 0.000000] [<ffffffff814863b0>] ? acpi_get_table_with_size+0x63/0xb9 [ 0.000000] [<ffffffff81dba141>] detect_intel_iommu+0x5f/0xf4 [ 0.000000] [<ffffffff817c3d20>] ? xen_swiotlb_init+0x4f0/0x4f0 [ 0.000000] [<ffffffff81d73c3b>] pci_iommu_alloc+0x50/0x6c [ 0.000000] [<ffffffff81d85809>] mem_init+0x17/0xa4 [ 0.000000] [<ffffffff81d68e2e>] start_kernel+0x281/0x4b7 [ 0.000000] [<ffffffff81d68120>] ? early_idt_handler_array+0x120/0x120 [ 0.000000] [<ffffffff81d68332>] x86_64_start_reservations+0x2a/0x2c [ 0.000000] [<ffffffff81d68480>] x86_64_start_kernel+0x14c/0x16f [ 0.000000] ---[ end trace bfe5b725f14adff3 ]---