From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 27 20:33:08 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 A67BB106566B for ; Wed, 27 Aug 2008 20:33:08 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 7F6AB8FC08 for ; Wed, 27 Aug 2008 20:33:08 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so49815rvf.43 for ; Wed, 27 Aug 2008 13:33:08 -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=XwkZxjhuyJSDBglTryKBT5NJblJRADmwoKB77dGyG5M=; b=Smfbuf3sz7MxE+V4tMNihSUUEkJjpL5bF0ouzO4vLG4/xaWetxljevufG6beV1XQli oFl3fWo8q1eb/BoQz8lVQJfDD5qcq91u+DETOevkLjWtk2JhPyTNsUFCpOrPl3d2xtrx xq4lnJxX67glxRfQ6E+E0iXS1IqwEmpyXABO8= 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=uYR1Im26EbIsjw6I8OR8/+yj7UlhiLexPwywFduvP2JfhzeuF8R59p+KK2UWHaTZKF J5sVdCOhYXQFSSlJlBQF6cdVUAE/0cBndObzSfQA6tmoeECh1J9/TMY3LLd9mmPF80QO Jrjc+BF7wjMRDgvlnxf17P+PHDR7Kj+kfQqCc= Received: by 10.141.82.20 with SMTP id j20mr250308rvl.234.1219869187915; Wed, 27 Aug 2008 13:33:07 -0700 (PDT) Received: by 10.140.127.19 with HTTP; Wed, 27 Aug 2008 13:33:07 -0700 (PDT) Message-ID: <3c0b01820808271333l34ead8ele99daab695baf667@mail.gmail.com> Date: Wed, 27 Aug 2008 16:33:07 -0400 From: "Alexander Sack" To: Ross In-Reply-To: <86689256.20080827112751@connection.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <13710393234.20080826164158@connection.ca> <48B46EE1.8060408@samsco.org> <3c0b01820808270743n5fd40995u6e9506b772f2b03c@mail.gmail.com> <86689256.20080827112751@connection.ca> Cc: freebsd-scsi@freebsd.org Subject: Re: Re[2]: 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: Wed, 27 Aug 2008 20:33:08 -0000 On Wed, Aug 27, 2008 at 11:27 AM, Ross wrote: > > AS> So one question I have is why doesn't the isp driver load the > AS> firmware in ispfw? [...clip...] By any chance do you have > AS> "hint.isp.0.fwload_disable" set? I'm not saying that will fix your > AS> problem but I just noticed this. Ok, I just wanted to make sure I wasn't going crazy! I've just patched the 6.x driver to load firmware again (without the use of the generic firmware driver which I believe came later). I still have to thoroughly test it. > The card came with 4.00.90 which is newer than the firmware included in > ispfw (4.00.20) - but to answer your question, yes, fwload_disable is > set for the cards. I believe that got set since there was some kind > of problem that we ran into at one point. I'll do some testing on > that. Please do but I think what you did is very reasonable. > AS> WARNING: this is pure speculation on my part from quickly looking at > AS> it. I'm just wondering if this is a bug in isp allowing the ASYNC > AS> events occuring before a complete attach has been performed. > > Apologies if it didn't come across in my previous message, that's > basically what I'm saying too. I have about a 50/50 chance of the > card booting successfully, and when it does, the output from the debug > lines is different, and it looks like the ASYNC event is executing > before it's time. (See the end of this message for the full output > from isp[01]: for a clean boot, since it's a long output.) Yea it looks like the loop down timer kthread gets started further down isp_attach() which I believe maybe the issue. I got to look at it some more. > AS> I'm assuming all you are doing is booting 7.0-RELEASE off the SAN? > > That is correct. We're just using the i386 image at the current time > (eventually going to amd64, but not now). It's been trimmed of the > fat, but nothing special/custom added in. Sure, thanks. > AS> As Scott asked, can you get a dump or a trace of the crash? > > See my other message to freebsd-scsi/Scott for that. Ummm, can you get more than what you posted? i.e. can you rebuild the kernel with options KDB options DDB which will enable the debugger. Then boot with a "-v" and when you get into a panic you should fall into the kernel debugger. At the prompt do a "t" and copy the output (you don't have to copy the addresses just the stack trace). I think I can imagine what it looks like but it would be better if you provided it. Another possibility is to obtain a dump: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN and post it. Thanks! -aps