From owner-freebsd-current@FreeBSD.ORG Thu Aug 18 01:24:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0143216A420 for ; Thu, 18 Aug 2005 01:24:52 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DBA43D53 for ; Thu, 18 Aug 2005 01:24:52 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) (authenticated bits=0) by aslan.scsiguy.com (8.13.3/8.13.3) with ESMTP id j7I1OhTg055958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 19:24:47 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Wed, 17 Aug 2005 19:24:43 -0600 From: "Justin T. Gibbs" To: Sam Lawrance , freebsd-current@freebsd.org Message-ID: In-Reply-To: <1123541407.832.16.camel@dirk.no.domain> References: <1123541407.832.16.camel@dirk.no.domain> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: adaptec 39320 - ahd0: Invalid Sequencer interrupt occurred X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 01:24:53 -0000 > I see the ahd0 message below on just about every boot of a dell sc1425 > running 6.0-BETA2, just after "waiting for scsi devices to settle". > Once the system is up I don't see it again. > > Is it harmful? Can I help? The machine has a serial cable attached so > it can be peeked and poked if need be. Sam, This message indicates that the firmware engine wound up in its interrupt handler with no status indicating an interrupt should have occurred. I'm not sure why this is happening in some configurations (yours is not the first), but it seems to be harmless enough. I would love to better understand why this is happening, but without being able to replicate the problem here (and I have tried), I don't think I can do much other than just turn off the message in the driver. -- Justin