Pardon me if this gets a bit long winded.

We have been using the Fsys.aha8scsi driver on our production systems for years (more than a decade actually), and are 
in the process of hardware upgrades.  After much evaluation and testing we decided on the Adaptec 29160P PCI based SCSII
 controller.  During all the evaluation and testing we really had no issues or problems withe the driver.  Now that our 
new systems have arrived and are being assembled, we have run into a rather strange set of issues...

Running show_pci reports that the Adaptec controller has vendor ID 9005 and Device ID x80.  So, we've been starting the 
Driver as 'Fsys.aha8scsi -L aha8scsi -D80 -V9005'.  This has been working just fine, until we tried it on one of our new
 systems.  At some point, usually during boot up, the driver prints this out on the console a couple times, and the 
machine locks up...

OSMEvent(0x0000a318, 0x0004, 00000000, ... )

Now here's where it gets weird. In the past we had used an older model Adaptec card and it had a device ID of xCF. In 
playing around with things to try to figure out what would work, on a whim we started the driver with -DCF.  It 
complains of errors parsing the command line, BUT IT WORKS!  And, even though we occasionally get an OSMEvent() lockup 
during boot up, if makes it past the bootup, it seems to be stable from there on.  It will always fail at some point 
with -D80 set.  

Anybody have any idea what could possibly be going on here?

BTW, the Adaptec controller is talking to an external ARC-6060 Series RAID controller (from Areca Technology 
Corporation).  One change in the mix from when we were evaluating and testing, the firmware in the RAID controller has a
 newer version.  Could that be causing this?

Any help or thoughts would be appreciated.

TIA//
-Rob