Bug 157586

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

Description of problem:
ES7000 systems won't boot with large configuration, because of legacy code that enforces I/O APIC ID's to be unique system wide. Unique I/O APIC ID only makes sense with Intel processors older than Xeons, that were utilizing serial APIC bus for interrupt delivery. With front side bus architecture, where I/O APIC IDs are not used, this check is obsolete, and also harmful when tries to re-assign the IDs on systems like ES7000, that employ Intel's P64H2 chipset. The IDs of its I/O APICs  are only 4 bit wide and cannot be assigned unique numbers.
Recently, this issue was discussed on LK, and two patches dealing with it were submitted and accepted in the main line, see http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm1/broken-out/:

do-not-enforce-unique-io_apic_id-check-for-xapic-systems-i386.patch
remove-unique-apic-io-apic-id-check.patch - for x86_64

The patches were tested on generic Intel boxes and ES7000, both IA-32 and x86_64. 
Since the patches are critical for our release, and appear to be low risk, we would like them to be included it in your kernel for the next update.

Version-Release number of selected component (if applicable):
2.6.X

How reproducible:
Always

Steps to Reproduce:
1. Boot x86_64 ES7000 that was configured with two cells
2. Watch the screen hang after the initial message
3. 
  

Actual Results:  We used ITP to see the actual problem, or it can also be done with early_printk configured. The system paniced with error message "IOAPIC[12]: Unable change apic_id!"

Expected Results:  The boot should've proceeded normally.

Additional info: