From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 18 17:24:48 2012 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 64E261065720; Wed, 18 Jul 2012 17:24:48 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0538FC1A; Wed, 18 Jul 2012 17:24:48 +0000 (UTC) Received: from [192.168.135.103] (c-76-126-166-136.hsd1.ca.comcast.net [76.126.166.136]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q6IHOkan003723 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Jul 2012 10:24:47 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <5006F15A.5060709@feral.com> Date: Wed, 18 Jul 2012 10:24:42 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Trent Nelson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Wed, 18 Jul 2012 10:24:48 -0700 (PDT) Cc: "freebsd-scsi@freebsd.org" Subject: Re: dev/isp panic (was Re: CAM Target Layer and dev/isp) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2012 17:24:48 -0000 On 7/18/2012 8:58 AM, Trent Nelson wrote: > Hmm, just to clarify, do you mean "the isp tried to print something > that blew up ACPI", or "ACPI blew up whilst isp just happened to be > printing something"? Would knowing what isp was trying to print be of > any help? (I can poke around the *putc buffers if it happens again.) > I'm not surprised that ACPI is involved, though. This box has always > seemed to run into ACPI issues (HP ProLiant DL585 G1, quad dual-core > Opteron, 64GB RAM), like hanging on boot during the pci->bios probe > stuff from a kernel circa 2-3 months ago. Trent. I wouldn't know. Since there are a limited number of printfs from isp_async you could probably narrow it down. Try booting with ACPI disabled. Or upgrade f/w.