Bug 177477
Summary: | Kernel panic - not syncing: PCI-DMA:high address but no IOMMU | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Orla Hegarty <ohegarty> |
Component: | kernel | Assignee: | Jim Paradis <jparadis> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron, netllama, peterm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-15 17:36:25 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
Orla Hegarty
2006-01-10 23:11:11 UTC
Here is further information concerning the kernel panic message .. ACPI: ( Supports S0 S1 S2 S3 S4 S5 ) ACPI Wakeup devices: PC10 COM1 KBC0 MSE0 USB0 USB2 P2P0 XVR0 XVR1 XVR2 XCR0 XCR1 md: Autodetecting RAID array. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem) Greetings. anaconda installer init version 10.1.1.25 starting mounting /proc filesystem ... DONE mounting /dev/pts (unix98 pty) filesystem ... DONE mounting /sys filesystem ... DONE trying to remount root filesystem read write ... done mounting /tmp as ramfs ... DONE running install ... running /sbin/loader Kernel panic - not syncing: PCI-DMA:high address but no IOMMU OK there must be an existing bug open for this one. Not sure which one though from my quick glance around. WORKAROUND ---------- 1. Go into the bios -> Advanced -> MCFG Table 2. Set the option to DISABLED Note the description for this option is as follows: "This feature needs to be disabled for some linux version to work with devices on PCI-X Slots correctly. Example. RHAS 4.0 Update 1 (32 bits or 64 bits)" So this is a known problem for Red Hat Enterprise Linux 4.0 U1 and is still a problem in U2. > there must be an existing bug open for this one. Can you check BZ#169115 to see if it is similiar issue that you are running into? Sorry I missed your comment / update. I took a look at the other bug and it sure looks like the same problem. I am going to go ahead and mark my bug as a duplicate of that one. Thanks for pointing it out !!! *** This bug has been marked as a duplicate of 169115 *** |