Bug 62807

Summary: 4.9 SMP does not work with Compaq Smart Array 3200
Product: Base System Reporter: Crow Leader <enemy5000>
Component: i386Assignee: Remko Lodder <remko>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.9-RELEASE   
Hardware: Any   
OS: Any   

Description Crow Leader 2004-02-13 23:40:21 UTC
same problem as bug 31035, I'm using a Compaq DL380 with latest P17 firmware (December 2002 release) and latest firmware 4.5 on the smart array 3200. Any kernel less SMP support works on this machine, enabling SMP causes it to fail to mount the boot drive.

How-To-Repeat: Compile SMP kernel, use machine with Smart Array 3200 RAID controller
Comment 1 kama 2004-02-25 09:47:09 UTC
FreeBSD 4.9-STABLE works with SMP on a Compaq DL380 with the SA3200.

What I had to do after erase with the compaq smart start, was to choose
Linux as the operating system to be installed.

Been running it since oct 2003 without any problem.

FreeBSD 4.9-STABLE FreeBSD 4.9-STABLE #2: Thu Dec  4 12:47:08 CET 2003

10:46AM  up 81 days, 22:31, 1 user, load averages: 0.00, 0.00, 0.00

dmesg.boot:

...
FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  8, version: 0x00220011, at 0xfec00000
...
ida0: <Compaq Smart Array 3200 controller> port 0x4000-0x40ff mem
0xc6ffff00-0xc6ffffff irq 15 at device 0.0 on pci1
ida0: drives=1 firm_rev=4.32
idad0: <Compaq Logical Drive> on ida0
idad0: 17363MB (35561280 sectors), blocksize=512
...
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0
intpin 2
APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
ata0-slave: ATAPI identify retries exceeded
SMP: AP CPU #1 Launched!
...

Cheers,
Bjorn
Comment 2 Remko Lodder freebsd_committer freebsd_triage 2006-09-03 23:32:39 UTC
State Changed
From-To: open->feedback

Eventhough i read that someone had solved this problem already 
can you tell me whether you still have this problem using 
recent FreeBSD versions? (like 6.1) 

After that we can see what needs to be done. Thanks! 


Comment 3 Remko Lodder freebsd_committer freebsd_triage 2006-09-03 23:32:39 UTC
Responsible Changed
From-To: freebsd-i386->remko

Grab the PR
Comment 4 Remko Lodder freebsd_committer freebsd_triage 2006-09-11 11:09:48 UTC
State Changed
From-To: feedback->closed

feedback timeout