Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 173895

Summary: Kernel panic on install on 64BG EM64T
Product: Red Hat Enterprise Linux 4 Reporter: Bastien Nocera <bnocera>
Component: kernelAssignee: Geoff Gustafson <grgustaf>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: dale.l.busacker, dely.l.sy, jbaron, keve.a.gabbert, lwoodman, venkatesh.pallipadi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0575 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 21:36:17 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:
Bug Depends On:    
Bug Blocks: 181409, 185624, 198694    
Attachments:
Description Flags
swiotlb_init_07.patch
none
x86_64_bootmem_alloc_fix.patch
none
x86_64_bootmem_alloc_fix.patch
none
x86_64_bootmem_alloc_fix.patch
none
x86_64_move_memmap_alloc_end.patch none

Description Bastien Nocera 2005-11-22 10:31:57 UTC 
Using RHEL4 U2's installer, a 64GB EM64T machine would panic on bootup with:
  Kernel panic - not syncing: map_single: bounce buffer is not DMA'ble 

"
The problem is because of mem_map using up most of the low memory (because of
64GB physical memory) and kernel is not  able to allocate swiotlb buffer in low
memory. We have verified that things work fine by moving the swiotlb init earlier.
"

Patch from venkatesh.pallipadi attached.
Comment 1 Bastien Nocera 2005-11-22 10:32:03 UTC 
Created attachment 121337 [details]
swiotlb_init_07.patch
Comment 3 Larry Woodman 2005-11-24 16:45:28 UTC 
This patch will work but another/better solution is to move the mem_map above
the 4GB boundary.  There is no reason that it needs to be at such a low address.
I'll work with Intel on creating a patch that does this.

Larry Woodman
Comment 8 Bob Johnson 2006-04-11 15:53:11 UTC 
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 4.4 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 4.4 release.
Comment 9 Bastien Nocera 2006-04-18 10:11:44 UTC 
Created attachment 127908 [details]
x86_64_bootmem_alloc_fix.patch
Comment 10 Bastien Nocera 2006-04-18 10:27:39 UTC 
Created attachment 127909 [details]
x86_64_bootmem_alloc_fix.patch
Comment 11 Bastien Nocera 2006-04-18 10:55:55 UTC 
Created attachment 127910 [details]
x86_64_bootmem_alloc_fix.patch
Comment 12 Bastien Nocera 2006-04-18 12:26:41 UTC 
Created attachment 127914 [details]
x86_64_move_memmap_alloc_end.patch
Comment 13 Bastien Nocera 2006-04-18 12:27:50 UTC 
Updated patches attached.
Comment 14 Jason Baron 2006-04-27 15:07:25 UTC 
committed in stream U4 build 34.25. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 20 Red Hat Bugzilla 2006-08-10 21:36:26 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0575.html