Bug 495603
| Summary: | Kernel warning: Your BIOS is broken; DMAR reported at address zero! | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gustavo Maciel Dias Vieira <gustavo> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | devin, gowdy, itamar, kernel-maint, mhlavink, nsoranzo, orca.simwe, plarsen, sgruszka, sid, tadej.j, thangpaserto |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-01 17:33:02 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: | |||
|
Description
Gustavo Maciel Dias Vieira
2009-04-14 01:22:59 UTC
It means just what it says (the warning was just added recently.) Report it to HP. While I wait for the Linux loving guys at HP to fix it, is there a way to silence or ignore the warning? Or at least, make it not look like a kernel oops that is picked by kerneloops on my desktop? (In reply to comment #2) > While I wait for the Linux loving guys at HP to fix it, is there a way to > silence or ignore the warning? Or at least, make it not look like a kernel oops > that is picked by kerneloops on my desktop? You can disable the iommu by adding 'intel_iommu=off' to the boot options. Even with 'intel_iommu=off' in the boot options, confirmed by "Intel-IOMMU: disabled" in dmesg, the warning still appears. As far as I know, my CPU does not have any type of virtual machine support (I wish it had...). Current kernel: 2.6.29.5-191.fc11.x86_64 Any other workaround? Getting the same error on a Dell. Did not get this error with the F11 kernel (only is F12). I have an Acer Aspire 1410-2285 notebook and also have to add the intel_iommu=off to boot. I keep getting the same alert message as everyone else. Kernel warning: Your BIOS is broken; DMAR reported at address zero! Same kind of error on HP notebook - I wonder if I disable intel_iomm if will have any effect on KVM? WARNING: at drivers/pci/dmar.c:598 check_zero_address+0x96/0x19b() (Not tainted) Hardware name: HP EliteBook 8530p Your BIOS is broken; DMAR reported at address zero! BIOS vendor: Hewlett-Packard; Ver: 68PDV Ver. F.0F; Product Version: F.0F Modules linked in: Pid: 0, comm: swapper Not tainted 2.6.31.12-174.2.3.fc12.x86_64 #1 Call Trace: [<ffffffff81051710>] warn_slowpath_common+0x84/0x9c [<ffffffff81423973>] ? _etext+0x0/0x1 [<ffffffff8105177f>] warn_slowpath_fmt+0x41/0x43 [<ffffffff8173e7fe>] check_zero_address+0x96/0x19b [<ffffffff81262181>] ? acpi_tb_verify_table+0x57/0x5c [<ffffffff812617df>] ? acpi_get_table_with_size+0x5a/0xb4 [<ffffffff81423973>] ? _etext+0x0/0x1 [<ffffffff8173e915>] detect_intel_iommu+0x12/0x8c [<ffffffff8171dbc3>] pci_iommu_alloc+0x5e/0x6c [<ffffffff8172d1a8>] mem_init+0x19/0x161 [<ffffffff81716be3>] start_kernel+0x20b/0x3fa [<ffffffff817162a1>] x86_64_start_reservations+0xac/0xb0 [<ffffffff8171639d>] x86_64_start_kernel+0xf8/0x107 BTW, I had this error but if I turn on VMX in the BIOS on my HP EliteBook 6930p it goes away. Warnings are about BIOS bug not kernel. same warning messages for my HP-DC7800 , CentOS 6.2 (2.6.32-279.el6.x86_64 #1 SMP) but it disappears after I switch on the virturalization option in BIOS (get into BIOS Security > System Security, and enable Virtualization Technology （VTx）and Virtualization Technology Directed I/O (VTd) After reboot, warning messages disappear. |