From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 24 20:14:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D711516A401; Fri, 24 Mar 2006 20:14:59 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DFCB43DA0; Fri, 24 Mar 2006 20:14:48 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2OKEjtb061436; Fri, 24 Mar 2006 13:14:46 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4424532E.30004@samsco.org> Date: Fri, 24 Mar 2006 13:14:38 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241057.59460.jhb@freebsd.org> <20060324192302.P797@brain.cc.rsu.ru> <200603241440.30487.jhb@freebsd.org> In-Reply-To: <200603241440.30487.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes 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: Fri, 24 Mar 2006 20:14:59 -0000 John Baldwin wrote: > On Friday 24 March 2006 13:12, Oleg Sharoiko wrote: > >>On Fri, 24 Mar 2006, John Baldwin wrote: >> >>JB>Hmm, well that interrupt storm is not due to a misrouted interrupt, it >>JB>might be a bug in the bge(4) driver. Can you try compiling a kernel w/o >>JB>USB and seeing if you can still reproduce the interrupt storm? >> >>Yes. >> >>db> show intrcnt >>irq1: atkbd0 2 >>irq4: sio0 3672 >>irq6: fdc0 6 >>irq9: acpi0 1 >>irq14: ata0 36 >>irq16: bge0 2592958 >>irq28: ips0 728 >>cpu0: timer 143147 > > > Hmm, you might need to look at bge(4) and figure out what condition it > is interrupting on, and why the driver isn't handling that condition. > > >>John, can you tell anything about another case, for which interrupt >>counters are: >> >>db> show intrcnt >>irq1: atkbd0 1 >>irq4: sio0 3 >>irq6: fdc0 2 >>irq9: acpi0 345147 >>irq14: ata0 1 >>cpu0: timer 57995 >> >>Does this also show an interrupt storm? This one has happened without bge >>in kernel. I'm asking because I've seen several different scenarios of >>hangs and this is from one of them. I'll try to reproduce all cases and >>gather interrupt statistics from all of them. I'm wondering can't all this >>cases be caused by one common reason behind all of them. > > > This just looks like you aren't getting interrups from devices at all. > 345,000 interrupts from scpi0 seems high. Scott