From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 30 21:16:40 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 E52251065678 for ; Tue, 30 Sep 2008 21:16:40 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id B6FD68FC1A for ; Tue, 30 Sep 2008 21:16:40 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so192435rvf.43 for ; Tue, 30 Sep 2008 14:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XJmjs5ZFCrPotmY7SiSGvg9a8S1zNEzs8wNWRQ8M39w=; b=xTUBFoSwV+lbRnZcjPm2DGxFrBihzsX4Ah77AVLhOU0OGUaVmyZfOgFH4Ll8evdmZP tsJgGlLm74kYsumGWe5KyS9QuetxiIsixv823Ljk+QJ+EncZkSIrXajFSxqxcEuNXSFy 6tsZhkhq9z82iF6mP4tx+I45uuAOrsffhmmwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=F590cTixyUShawPYQk2USqm9OoIeqR8ivreUVdi3RvVUBfGf0iMD/WZ6hT2f/M0baz FIoT8AYFGMWBqlifQp0ohKXhJYF9e6F6/g2d+qpJETVZnKIo4d4UYhWqWGc9ma956Rvk GEfbbNYltpfJnA4fYMYL7YqPBTk5M0RN2lVzA= Received: by 10.141.13.16 with SMTP id q16mr3883381rvi.99.1222809400251; Tue, 30 Sep 2008 14:16:40 -0700 (PDT) Received: by 10.141.136.21 with HTTP; Tue, 30 Sep 2008 14:16:39 -0700 (PDT) Message-ID: <3c0b01820809301416v416460e5gc0b4689febcf0905@mail.gmail.com> Date: Tue, 30 Sep 2008 17:16:39 -0400 From: "Alexander Sack" To: "Paul A. Procacci" In-Reply-To: <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200809250910.m8P9A4MY047099@freefall.freebsd.org> <835218108.20080925113214@connection.ca> <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com> Cc: freebsd-scsi@freebsd.org Subject: Re: 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 List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2008 21:16:41 -0000 On Thu, Sep 25, 2008 at 1:51 PM, Alexander Sack wrote: > On Thu, Sep 25, 2008 at 11:32 AM, Ross wrote: >> >> 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. > > > Yea totally. If you can get a stack trace that would be great (just > compile in the debugger support, reboot, and when you hit the panic do > a trace and just give us the function output (again exact addresses > not so much)). Paul do you have any update with this issue? I have my patches ready and I want to try to resolve yours if it indeed turns out to be a similar bug. Please let me know, -aps