Erik P. Ostlyngen
2006-Aug-09 07:23 UTC
Problems with QLogic 2312 FC controller on FreeBSD 4.11 stable
Hi, I'm struggling to get a QLogic 2312 FC controller to work with a FreeBSD 4.11 server after upgrading to the latest stable code in cvs. My server, an IBM-x336, is connected with fiber channel to a Nexsan SATABlade using the QLogic 2312 FC controller. I've been running 4.11-RELEASE for a while and this seemed to work, but had low performance on certain disk operations. I've now upgraded the kernel to 4.11-STABLE (cvs checkout 2006-08-07), and the external disk is no longer recognized after booting. Has anyone seen this before? Any suggestions on how to proceed? Some specs: Server: IBM-x336, 2GB ram, 2x3.2GHz CPU FC controller: QLogic 2312, using firmware from the FreeBSD ispfw module Disk raid: Nexsan SATABlade, firmware 9p41 With the 4.11-STABLE kernel, I get the following boot messages: Preloaded elf kernel "kernel" at 0xc066b000. Preloaded elf module "vinum.ko" at 0xc066b09c. Preloaded elf module "ispfw.ko" at 0xc066b13c. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 3 IOAPIC #0 intpin 23 -> irq 5 IOAPIC #0 intpin 17 -> irq 10 pci0: <PCI bus> on pcib0 pci0: <unknown card> (vendor=0x8086, dev=0x3591) at 0.1 pcib1: <PCI to PCI bridge (vendor=8086 device=3595)> irq 0 at device 2.0 on pci0 pci2: <PCI bus> on pcib1 pcib2: <PCI to PCI bridge (vendor=8086 device=3597)> irq 0 at device 4.0 on pci0 pci3: <PCI bus> on pcib2 pcib3: <PCI to PCI bridge (vendor=8086 device=0329)> at device 0.0 on pci3 IOAPIC #1 intpin 4 -> irq 11 pci4: <PCI bus> on pcib3 mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x4000-0x40ff mem 0xdefe0000-0xdefeffff,0xdeff0000-0xdeffffff irq 11 at device 1.0 on pci4 mpt0: MPI Version=1.2.15.0 mpt0: Capabilities: ( RAID-1 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) pcib4: <PCI to PCI bridge (vendor=8086 device=032a)> at device 0.2 on pci3 IOAPIC #2 intpin 0 -> irq 16 pci5: <PCI bus> on pcib4 isp0: <Qlogic ISP 2312 PCI FC-AL Adapter> port 0x5000-0x50ff mem 0xdcfff000-0xdcffffff irq 16 at device 1.0 on pci5 isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.19 isp0: 839 max I/O commands supported isp0: NVRAM Port WWN 0x210000e08b82cd8a ... (then no more reports from the isp driver, and no da2 device) With the 4.11-RELEASE kernel, I got these boot messages from the isp driver: isp0: <Qlogic ISP 2312 PCI FC-AL Adapter> port 0x5000-0x50ff mem 0xdcfff000-0xdcffffff irq 16 at device 1.0 on pci5 isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.1.20 isp0: Installed in 64-Bit PCI slot isp0: 744 max I/O commands supported isp0: NVRAM Port WWN 0x210000e08b82cd8a ... isp0: LIP Received isp0: Loop UP isp0: Port Database Changed ... isp0: Firmware State <Config Wait->Ready> isp0: 2Gb link speed/s isp0: Loop ID 0, AL_PA 0xef, Port ID 0xef, Loop State 0x2, Topology 'Private Loop' isp0: Target 0 (Loop 0x0) Port ID 0xef (role Initiator) Arrived Port WWN 0x210000e08b82cd8a Node WWN 0x200000e08b82cd8a isp0: Target 1 (Loop 0x1) Port ID 0xe8 (role Target) Arrived Port WWN 0x5000402001ec058f Node WWN 0x2001000402ec058f ... da2 at isp0 bus 0 target 1 lun 0 da2: <NEXSAN SATABl(C0A80103) 9p41> Fixed Direct Access SCSI-4 device da2: 200.000MB/s transfers, Tagged Queueing Enabled da2: 1907504MB (3906568192 512 byte sectors: 255H 63S/T 46564C) Best regards, Erik ?stlyngen