From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 25 15:32:15 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 F19F6106569A for ; Thu, 25 Sep 2008 15:32:15 +0000 (UTC) (envelope-from westr@connection.ca) Received: from nc-tor-mail2.connection.ca (nc-tor-mail2.connection.ca [205.207.122.27]) by mx1.freebsd.org (Postfix) with ESMTP id D001C8FC2D for ; Thu, 25 Sep 2008 15:32:15 +0000 (UTC) (envelope-from westr@connection.ca) Received: from localhost (external.tor.connection.ca [216.234.38.18]) by nc-tor-mail2.connection.ca (Postfix) with ESMTP id 1B29574E5DF for ; Thu, 25 Sep 2008 11:32:15 -0400 (EDT) Date: Thu, 25 Sep 2008 11:32:14 -0400 From: Ross Organization: Network Connection X-Priority: 3 (Normal) Message-ID: <835218108.20080925113214@connection.ca> To: freebsd-scsi@FreeBSD.org In-Reply-To: <200809250910.m8P9A4MY047099@freefall.freebsd.org> References: <200809250910.m8P9A4MY047099@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re[2]: kern/126866: [isp] [panic] kernel panic on card initialization X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ross List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 15:32:16 -0000 PAP> I am having the same exact problem you were having using the same PAP> device. I started receiving this error on FBSD7-RELEASE and thought it PAP> was specific to that version. Naturally I upgraded to FBSD7-Stable as PAP> of today (9/25/2008), but still haven't been able to resolve this error, PAP> even with the patch presented here. Like you had mentioned on PAP> freebsd-scsi, the machine panic's roughly 50% of the time during boot. Actually, going over the trap output, it looks different than the output I had, so it might be a different issue in the end. Which kernel are you running? (i386/amd64), and is it possible to get the output of a dmesg, so we know what chipset the driver thinks it is? (Are you running an HP Blade w QHM6432 like I am?) Also, if you can set 'hint.isp.[01].debug=0x11F' in your /boot/device.hints file, it'll hopefully give some additional output to help track the problem down. Obviously the best is to compile in the kernel debugger as that'll give the exact place it crashes. Thanks, Ross. -- Ross West Tel: +1 416 967 6767 Network Manager Fax: +1 416 967 7777 Network Connection Email: westr@connection.ca