DragonFly 3.4.3 crashes on SUN Blade X6250 with Qlogic ISP 2432 FC card
I'm a newbie with DragonFlyBSD, although I do have a long history administering OpenBSD servers and firewalls. I've spent the recent years in [Arch] Linux world, and am using DragonFly for the first time.
I've decided to apart from the Linuxverse in favor of Open- and DragonFlyBSD. What I love in Arch is the rolling release system, but security wise these two little devils are on a totally different level of course.
I'm working to get DragonFly (3.4.3) run on a SUN Blade X6250 and ran into a problem I can not solve without your help. I'd appreciate your time and effort to get this one sorted out with me! It's clearly the Qlogic ISP 2432 fibre channel card that's causing the crash, but I have no idea how to fix this - apart from removing the Qlogic controller, which allows the system to boot just fine. The server requires the fibre channel controller to work since all data is stored on an external FC array.
I'm booting from USB stick and have tried all the alternative boot options such as boot without AHCI etc. With x64 the screen gets filled with the kernel error message details so I can't tell what exactly happens right before the crash. After the crash nothing works, not even the CapsLock/NumLock lights, so I can't do anything at the debugger console.
The i386 version manages to tell me this before dying:
pcib0: pcibus 0 on motherboard
pci0: on pcib0
pcib1: at device 2.0 on pci0
pci1: on pcib1
pcib2: irq16 at device 0.0 on pci1
pci2: on pcib2
pcib3:MPTABLE PCI-PCI bridge> at device 0.0 on pci2
pcib3: Disable PCI Express hot-plug interrupts(0x003f)
pci3: on pcib3
isp0: port 0xb00-0xb8ff mem 0xc70fc000-0xc70fffff irq 16 at device 0.0 on pci3
isp0: Polled Mailbox Command (0x8) Timeout (100000us) started @ isp_reset:1028)
isp0: Mailbox Command 'ABOUT FIRMWARE' failed (TIMEOUT)
panic: assertion "l->lk_waitcont =00" failed in lockuninit at /usr/src/sys/kern/kern_lock.c:645
cpuid = 0
no kernel stack address
CPU0 stopping CPUs: 0x000000fe
Stopped at Debugger+0x3c: movb $0,in_Debugger.4852 ======================================================================
Looks like a bug to me.
I'd appreciate a lot any help you guys can provide! Please let me know if I can do anything to report this one better.