Description of problem:
In two Intel S3200SH server motherboards, one with the 33 version of the BIOS
and Xeon processor 3075, and another with the 39 version of the BIOS and Xeon
processor 3085, the 2.6.24 fedora 8 kernels generated the following boot error:
DMAR:DRHD (flags: 0x0000001c) base: 0x0000feb010000000
This error is written repeatedly on the screen and the system does not boot.
When trying to boot with argument "acpi = off", the systems boots, but the
kernel detects the Xeon 3075 or 3085 processor as single core.
The systems boot correctly with 2.6.23 kernels.
Version-Release number of selected component (if applicable):
All 2.6.24 kernels.
Update or install any 2.6.24 kernel in an Intel S3200SH server motherboard.
Steps to Reproduce:
1. Install the 2.6.24 kernel in an Intel server S3200SH motherboard.
2. Boot the system, the boot failed.
3. Put the acpi = off argument in the boot options, the system boot, but
cat /proc/cpuinfo report only one processor (processor 0).
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 3075 @ 2.66GHz
stepping : 11
cpu MHz : 2660.039
cache size : 4096 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm const
ant_tsc up arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2
ssse3 cx16 xtpr lahf_lm
bogomips : 5322.08
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
probably yet another case of buggy firmware. I think we're just going to have
to turn this off for now. The code needs to become a lot more tolerant of crap
It should boot with this option:
I sent a pointer to this bug to the upstream developers. hopefully they'll be
able to make their code handle cases like this automatically, but I really think
this code isn't ready for primetime just yet.
DMAR has been disabled in the 2.6.25 kernels for Fedora 8.
kernel-188.8.131.52-10.fc8 has been submitted as an update for Fedora 8
*** Bug 444420 has been marked as a duplicate of this bug. ***
kernel-184.108.40.206-10.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-4484
The update fixes the bug. The kernel boots properly without the option
intel_iommu = off
kernel-220.127.116.11-10.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 436899 has been marked as a duplicate of this bug. ***
I have this problem with Fedora 12 on Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
kernel panic - not syncing: DMAR hardware is malfunctioning
Just a guess but I think you're more likely to get a response to this if you open a new bug report for Fedora 12. This bug was for Fedora 8 which is no longer supported.
"Just a guess but I think you're more likely to get a response to this if you
open a new bug report for Fedora 12"
bug #540082 opened for FC12 on this issue
The "intel_iommu = off" resovle the kernelpanic, but it stop installation at startup installer here..
My notebook is hp compaq cq40 609tx.