From owner-freebsd-stable@FreeBSD.ORG Mon Feb 5 16:26:59 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F3BC16A407 for ; Mon, 5 Feb 2007 16:26:59 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id C123513C4BB for ; Mon, 5 Feb 2007 16:26:57 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so1285985uge for ; Mon, 05 Feb 2007 08:26:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JEDXNRaFSyD+HanWwp/9HTxdZCsZDQoVwGJ2XTs3PgE7XEDTQJ+NgcqcqpFJrHC/HfMkbEI8ZcwdSmBOIaEorv+v7ehXC7NBqEyZoIydNLg7AxSCzg7tn+YT1TQgKuwG3I1w2k0Q3NKSQcax0Jc05ZnMTDYWD04aCuBd/FsKlU4= Received: by 10.78.17.4 with SMTP id 4mr1110701huq.1170691230202; Mon, 05 Feb 2007 08:00:30 -0800 (PST) Received: by 10.78.199.19 with HTTP; Mon, 5 Feb 2007 08:00:30 -0800 (PST) Message-ID: <7579f7fb0702050800x3b9fbc86j2908a2ee193d8713@mail.gmail.com> Date: Mon, 5 Feb 2007 08:00:30 -0800 From: "Matthew Jacob" To: "Eduardo Meyer" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: stable@freebsd.org Subject: Re: Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 16:26:59 -0000 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 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 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 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@gmail.com > profissional: ddm.farmaciap@saude.gov.br > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >