Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device

[Matthew Jacob]

Helpful information would be:

  a) Release
  b) Connection Topology

It looks like you're going through a switch. Your short term solution
will be to zone your box and the CX300 together excluding all else.

A longer term solution is for me to MFC the new SAN evaluation code
which is a bit less harsh.

On 2/5/07, Eduardo Meyer <dudu.meyer at gmail.com> wrote:
> Hello gentlemen,
>
> I have a QLogic FC card in a FreeBSD, connected to a CX300 storage
> which sometimes looses connection with no aparent reason. If someone
> had lived a similar problem or know of something that would help
> diagnose the cause, I would like to hear.
>
> When the problem happens all I get in the logs is:
>
> Feb  5 01:01:37 mailsrvr kernel: isp0: Name Server Database Changed
> Feb  5 01:01:37 mailsrvr kernel: isp0: Firmware State <Config Wait->Ready>
> Feb  5 01:01:37 mailsrvr kernel: isp0: Target 126 (Loop 0x7e) Port ID
> 0xfffffe (role (none)) Arrived
> Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x200500051e034ad8
> Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x100000051e034ad8
> Feb  5 01:01:37 mailsrvr kernel: isp0: 2Gb link speed/s
> Feb  5 01:01:37 mailsrvr kernel: isp0: Loop ID 255, Port ID 0x10500,
> Loop State 0x2, Topology 'F Port'
> Feb  5 01:01:37 mailsrvr kernel: isp0: Target 255 (Loop 0xff) Port ID
> 0x10500 (role Initiator) Arrived
> Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x210000e08b925d0e
> Feb  5 01:01:37 mailsrvr kernel: isp0: Name Server Database Changed
> Feb  5 01:01:37 mailsrvr kernel: isp0: Firmware State <Config Wait->Ready>
> Feb  5 01:01:37 mailsrvr kernel: isp0: Target 126 (Loop 0x7e) Port ID
> 0xfffffe (role (none)) Arrived
> Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x200500051e034ad8
> Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x100000051e034ad8
> Feb  5 01:01:37 mailsrvr kernel: isp0: 2Gb link speed/s
> Feb  5 01:01:37 mailsrvr kernel: isp0: Loop ID 255, Port ID 0x10500,
> Loop State 0x2, Topology 'F Port'
> Feb  5 01:01:37 mailsrvr kernel: isp0: Target 255 (Loop 0xff) Port ID
> 0x10500 (role Initiator) Arrived
> Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x210000e08b925d0e
> Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x200000e08b925d0e
> Feb  5 01:01:37 mailsrvr kernel: isp0:   Fabric Device @ PortID 0x10400
> Feb  5 01:01:37 mailsrvr kernel: isp0:   Fabric Device @ PortID 0x10500
> Feb  5 01:01:37 mailsrvr kernel: isp0: Target 0 (Loop 0x1) Port ID
> 0x10000 (role Target) Departed
> Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x500601603022db3d
> Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x50060160b022db3d
> Feb  5 01:01:37 mailsrvr kernel: (da0:isp0:0:0:0): lost device
> Feb  5 01:01:37 mailsrvr kernel: isp0: Retained login of Target 1
> (Loop ID 0x2) Port 0x10400
>
> and later, FreeBSD freezes (sometimes it panics).
>
> It is not very often that it happens, and it is under completly random
> circunstances (sometimes high load, sometimes the lowest load, on
> different hours, etc).
>
>
> --
> ===========
> Eduardo Meyer
> pessoal: dudu.meyer at gmail.com
> profissional: ddm.farmaciap at saude.gov.br
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>