From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 18:43:42 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 C423916A403; Mon, 10 Apr 2006 18:43:42 +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 2DAEE43D49; Mon, 10 Apr 2006 18:43:39 +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 k3AIhau0032836; Mon, 10 Apr 2006 12:43:37 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <443AA752.3070304@samsco.org> Date: Mon, 10 Apr 2006 12:43:30 -0600 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> <20060328201134.S763@brain.cc.rsu.ru> <20060406223724.S1099@wolf.os.rsu.ru> <200604101401.12479.jhb@freebsd.org> In-Reply-To: <200604101401.12479.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.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) 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: Mon, 10 Apr 2006 18:43:42 -0000 John Baldwin wrote: > On Thursday 06 April 2006 15:07, Oleg Sharoiko wrote: > >>Hi, that's me again. >> >>John, I've got more information on my problem: >> >>It looks like the mis-routed interrupt is the one from ips. In my kernel >>ips is on vector 49 and bge is on vector 60. I've added >> >> if (vector == 60) >> vector = 49; >> >>to sys/amd64/amd64/local_apic.c and I have no more interrupt storm until >>bge really generates interrupt. Am I right with my conclusion about ips >>interrupt being mis-directed to bge? > > > Well, the vectors is the wrong thing to mess with as vector's are IDT > entries. > > >>There's also another interesting point: it looks like ips triggers >>interrupt on both vectors (49 and 60 - irq 28 and irq 16). Why do I think >>so? > > > This happens in several machines with Intel server chipsets due to a bug > in the PXH host bridges with no real workaround. > Well, the work around is to not mask the APIC and instead let the driver handle masking or ACKing the interrupt =-) It sucks that there are undocumented gotchas like this in the PC platform, but it is important to acknowledge them. Scott