From owner-freebsd-current Tue Jun 26 11:21:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 7677B37B409; Tue, 26 Jun 2001 11:21:33 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f5QILVU22240; Tue, 26 Jun 2001 12:21:31 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200106261821.f5QILVU22240@aslan.scsiguy.com> To: Dave Cornejo Cc: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: SCSI hangs w/SuperMicro 6010H In-Reply-To: Your message of "Tue, 26 Jun 2001 11:18:41 PDT." <200106261818.f5QIIfg20434@white.dogwood.com> Date: Tue, 26 Jun 2001 12:21:31 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> That won't catch all interrupts. Most notably, you won't know >> if commands are completing. Command completions are much more >> prevalent than sequencer or scsi interrupts. > >should I try and catch the command completions? which routine is best >to do this in? ahc_intr() in aic7xxx_inline.h gates all interrupt activity. I don't know that it will tell you why you are hung though. All that is clear is that interrupts at least work for a time. >btw, thanks very much for your help! Sure. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message