Bug 443902
| Summary: | RT kernel panic: gart_iommu_hole_init() fails to allocate aperture memory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Clark Williams <williams> | ||||
| Component: | realtime-kernel | Assignee: | Steven Rostedt <srostedt> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 1.0 | CC: | bhu, duck, jburke, lgoncalv, mschmidt, williams | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| URL: | http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=2811732 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 2.6.24.7-71.el5rt | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-12-16 15:32:13 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: | |||||||
| Attachments: |
|
||||||
|
Description
Clark Williams
2008-04-23 22:51:54 UTC
test logs with backtraces: http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=2811732 Where are we on this bug? I've seen a couple of panics in RHTS with this system and I wonder if we have bad h/w or if we need to ask the lab guys to change a BIOS setting? Looks like CONFIG_DMAR was the culprit. Fixed in -71 Clark, Looks like it is back in 2.6.24.7-75.el5rt :( http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=3785310 <snip> Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Cannot allocate aperture memory hole (ffff810100000000,65536K) Kernel panic - not syncing: Not enough memory for aperture Pid: 0, comm: swapper Not tainted 2.6.24.7-75.el5rt #1 Call Trace: [<ffffffff8103ca80>] panic+0xaf/0x160 [<ffffffff814b8aa7>] ? __alloc_bootmem_nopanic+0x31/0x5c [<ffffffff814b1ee0>] gart_iommu_hole_init+0x4b7/0x582 [<ffffffff8105fe60>] ? rt_up+0x29/0x52 [<ffffffff8128d621>] ? _etext+0x0/0x3fbf [<ffffffff814ac3a1>] pci_iommu_alloc+0x9/0x15 [<ffffffff814b3460>] mem_init+0x24/0x16d [<ffffffff814a4aa2>] start_kernel+0x258/0x329 [<ffffffff814a4119>] _sinittext+0x119/0x120 </snip> bumping priority/severity and reassigning to rostedt Tried modifying the allocation mechanism in arch/x86/kernel/aperture_64.c, from using __alloc_bootmem_nopanic() to __alloc_bootmem_low() and got the following panic message: Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM low bootmem alloc of 67108864 bytes failed! Kernel panic - not syncing: Out of low memory Pid: 0, comm: swapper Not tainted 2.6.24.7-rt14 #4 Call Trace: [<ffffffff8103ca94>] panic+0xaf/0x160 [<ffffffff814b8829>] ? __alloc_bootmem_core+0x12c/0x2e5 [<ffffffff814b8a6d>] __alloc_bootmem_low+0x73/0x7c [<ffffffff814b1e52>] gart_iommu_hole_init+0x429/0x582 [<ffffffff8105fe74>] ? rt_up+0x29/0x52 [<ffffffff8128d631>] ? _etext+0x0/0x3fbf [<ffffffff814ac3a1>] pci_iommu_alloc+0x9/0x15 [<ffffffff814b3460>] mem_init+0x24/0x16d [<ffffffff814a4aa2>] start_kernel+0x258/0x329 [<ffffffff814a4119>] _sinittext+0x119/0x120 (full boot log attached) Created attachment 313513 [details]
boot log of kernel with aperture alloc changed to __alloc_bootmem_low
*** This bug has been marked as a duplicate of bug 466341 *** |