[Bug 43243] Megaraid panic in Dapper Beta 1 & 2 installers [amd64]

[M]

Public bug reported:

Affects: linux-source-2.6.15 (Ubuntu)
       Severity: Normal
       Priority: (none set)
         Status: Unconfirmed


Description:
When booting the AMD64 Dapper Beta 1 or 2 install cds on a dual opteron
244 system with a Megaraid Elite 1600 (Megaraid 493) controller, I get
the messages below in dmesg and then some (short - 1-5min) period later
a kernel panic. I haven't been able to get the call trace, but the
kernel panic says "Aiee, killing interrupt handler!".

This problem also occurred in Breezy, but **was fixed in Dapper Flight
6** (and is now broken again :( ).

The gory details:

Megaraid driver version: 2.20.4.6 (March 7 2005)
Megaraid cmm version: 2.20.2.6

dmesg says:

Scanning scsi channel 0 [Phy 0] for non-raid devices
megaraid aborting-1 cmd=12 <c=0 t=0 l=0>
megaraid abort: 1:0[0:0], fw owner
megaraid mbox: Wait for 1 commands to complete: 180
...
(This keeps display, at 5 second intervals and the timer decreasing in line)
megaraid mbox: critical hardware error!
megaraid: hw error, cannot reset
megaraid: hw error, cannot reset
4:0:0:0 scsi: Device offlined - not ready after error recovery

I've tried booting with the following kernel options (seperately):
acpi=off
noapic
iommu=force
iommu=noforce

None made a difference.

The card is on the latest BIOS (F320) and firmware (111U) revisions.

-- 
Megaraid panic in Dapper Beta 1 & 2 installers [amd64]
https://launchpad.net/bugs/43243