Speaking of Fibre-channel problems...

[Tom Samplonius]

Tim,

   This is interesting.  Does it also happen with the 32bit version of FreeBSD? 
Is it possibly a 4+GB RAM problem where the isp driver has problems accessing 
high memory?  You might want to try the 32bit version, and limiting FreeBSD to 
3.5GB of RAM.  I've heard that the mpt driver had (or still has) 4+GB memory 
problems.

Tom



On Tue, 7 Feb 2006, Tim Spencer wrote:

> 	I've been using qlogic 2312 FC cards in my FreeBSD 4.11 hosts without 
> problems (aside from lack of multipathing and so on :-), but when I tried to 
> use them in a new AMD64 SMP FreeBSD 6.x host that I'm trying to qualify for 
> our production environment, I'm having problems.  The card doesn't seem to be 
> able to join the fabric.  The card's LEDs both light up while the system is 
> booting, but after the isp driver initializes, it just goes to a yellow 
> blinky light which I have come to associate with "I have not been initialized 
> correctly".  I turned on CAMDEBUG and hacked isp_prt to print everything out, 
> and this is what I got during the boot up:
>
> ... (hundreds of repeats of the next 3 lines)
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40008010
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: usec1998392: 0xdcc880dc->0xdcd86a92 
> enano 0x0000fe9b6
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40008010
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: usec1999434: 0xdcde08dd->0xdcede8c1 
> enano 0x0000fdfe4
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: kthread: FC state ungood
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: kthread: waiting until called
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010
> Feb  7 17:02:25 Xsc-db3 kernel: acd0: CDROM <TEAC CD-ROM CD-224E/K.9A> at 
> ata0-master UDMA33
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4
> Feb  7 17:02:25 Xsc-db3 last message repeated 4 times
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 901
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 901
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4
> Feb  7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4
> ... (hundreds of repeats of the previous 3 lines)
>
> 	Unfortunately, I don't have the start of all this, because it filled 
> the dmesg space up and scrolled it off the top.  Here's some more info on the 
> system:
>
> : Xsc-db3.soma.ironport.com []#; uname -a
> FreeBSD Xsc-db3.soma.ironport.com 6.0-STABLE FreeBSD 6.0-STABLE #1: Tue Feb 
> 7 16:47:28 PST 2006     root at Xsc-db3.soma.ironport.com:/usr/ 
> obj/usr/src/sys/MESSAGING_GATEWAY.amd64_INSTALL  amd64
> : Xsc-db3.soma.ironport.com []#;
>
> I have this in MESSAGING_GATEWAY.amd64_INSTALL:
>
> # tspencer temporary hack
> options CAMDEBUG
> options CAM_DEBUG_BUS=-1
> options CAM_DEBUG_TARGET=-1
> options CAM_DEBUG_LUN=-1
> # Qlogic FC card stuff
> device         isp             # Qlogic family
> device         ispfw           # Firmware for QLogic HBAs- normally a module
>
> 	Anyways, has anybody else solved this sort of problem?  And if not, 
> does anybody have any suggestions as to how to figure out what is going 
> wrong?  Thanks, and have fun!
>
> 		-tspencer
>
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"
>