From owner-freebsd-current Tue Jun 26 11:18:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id E921737B405; Tue, 26 Jun 2001 11:18:48 -0700 (PDT) (envelope-from dave@dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.11.4/8.11.3) id f5QIIfg20434; Tue, 26 Jun 2001 11:18:41 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200106261818.f5QIIfg20434@white.dogwood.com> Subject: Re: SCSI hangs w/SuperMicro 6010H In-Reply-To: <200106261440.f5QEe8U17052@aslan.scsiguy.com> "from Justin T. Gibbs at Jun 26, 2001 08:40:08 am" To: "Justin T. Gibbs" Date: Tue, 26 Jun 2001 11:18:41 -0700 (PDT) Cc: Dave Cornejo , John Baldwin , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Justin T. Gibbs wrote: > >John Baldwin wrote: > >> Hrmm, perhaps you are getting an interrupt storm from ahc. Ok, try > >> this: find the ahc driver's interrupt handler, and add a printf. > >> Then see if the printf fires while the machine is hung. > > > >Ok, I put a printf in ahc_handle_seqint() and ahc_handle_scsiint(). > > 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? btw, thanks very much for your help! dave c -- Dave Cornejo @ Dogwood Media, Fremont, California (also dcornejo@ieee.org) "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message