From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 24 20:14:13 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 8F7E016A41F; Fri, 24 Mar 2006 20:14:13 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB01A43D69; Fri, 24 Mar 2006 20:14:11 +0000 (GMT) (envelope-from os@rsu.ru) Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k2OKE3Rm086975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Mar 2006 23:14:05 +0300 (MSK) (envelope-from os@rsu.ru) Date: Fri, 24 Mar 2006 23:14:03 +0300 (MSK) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <200603241440.30487.jhb@freebsd.org> Message-ID: <20060324230940.K11040@brain.cc.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241057.59460.jhb@freebsd.org> <20060324192302.P797@brain.cc.rsu.ru> <200603241440.30487.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean 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:13 -0000 On Fri, 24 Mar 2006, John Baldwin wrote: JB>Hmm, you might need to look at bge(4) and figure out what condition it JB>is interrupting on, and why the driver isn't handling that condition. I'll try... JB>> John, can you tell anything about another case, for which interrupt JB>> counters are: JB>> JB>> db> show intrcnt JB>> irq1: atkbd0 1 JB>> irq4: sio0 3 JB>> irq6: fdc0 2 JB>> irq9: acpi0 345147 JB>> irq14: ata0 1 JB>> cpu0: timer 57995 JB>> JB>> Does this also show an interrupt storm? This one has happened without bge JB>> in kernel. I'm asking because I've seen several different scenarios of JB>> hangs and this is from one of them. I'll try to reproduce all cases and JB>> gather interrupt statistics from all of them. I'm wondering can't all this JB>> cases be caused by one common reason behind all of them. JB> JB>This just looks like you aren't getting interrups from devices at all. Why do you think so? This case has happened in the middle of boot even before disks were started and the kernel hasn't printed anything about disks it has detected. It looks normal to me that just a few interrupts has been triggered. But irq9 looks quite suspicious, isn't it? Can it be possible that by some reason interrupt storms are triggered on different irq lines resulting in different behaviour? -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University.