From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 26 21:00:29 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D1071065676 for ; Tue, 26 Aug 2008 21:00:29 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 97AE18FC1A for ; Tue, 26 Aug 2008 21:00:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id m7QL0HKO051152; Tue, 26 Aug 2008 15:00:17 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48B46EE1.8060408@samsco.org> Date: Tue, 26 Aug 2008 15:00:17 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Ross References: <13710393234.20080826164158@connection.ca> In-Reply-To: <13710393234.20080826164158@connection.ca> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: isp(4) - kernel panic on initialization of driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2008 21:00:29 -0000 Ross wrote: > I've been tracking down a problem that is sometimes causing a kernel > panic to occur when initializing the isp driver in the system. (System > in question is a HP Blade - BL460c w/ QHM 6432 FC dual port card > reporting as the following: > > isp0: port 0x4000-0x40ff mem 0xfdff0000-0xfdff3fff irq 18 at device 0.0 on pci16 > isp0: Board Type 2422, Chip Revision 0x2, resident F/W Revision 4.0.90 > isp1: port 0x4400-0x44ff mem 0xfdfe0000-0xfdfe3fff irq 19 at device 0.1 on pci16 > isp1: Board Type 2422, Chip Revision 0x2, resident F/W Revision 4.0.90 > > We're doing a boot-via-san situation, and the issue looks to be that > the card is receiving a ISPASYNC_CHANGE_PDB command on isp1 before > it's ready for it. I'm guessing it's due to the fact the card already > as the firmware loaded and active (due to the boot). > > Console debug (hint.isp.[01].debug=0x11f) output looks like the following on a crash: > > -= > kernel: isp1: port 0x4400-0x44ff mem 0xfdfe0000-0xfdfe3fff irq 19 at device 0.1 on pci16 > kernel: isp1: set PCI latency to 64 > kernel: isp1: [ITHREAD] > kernel: isp1: line 5345: markportdb > kernel: isp1: Port Database Changed > kernel: isp1: Port Database Changed: freeze simq (loopdown) > [crash] > -= > > Further debugging shows that isp_freeze_loopdown() function that is > called at the above point never returns. Quick guess is the called > xpt_freeze_simq() function [line 290 in isp_freebsd.c] is the culprit, > but that's about the limit of my ability for tracking this down. > > > If anyone has any pointers to fixing this, that would be appreciated! > > Thanks, > Ross. > > (Also filed http://www.freebsd.org/cgi/query-pr.cgi?pr=126866 with > basically the same notes above) > Please post the panic trace and messages. Scott