From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 08:59: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 8313816A420; Sun, 26 Feb 2006 08:59:59 +0000 (GMT) (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 CD4F543D48; Sun, 26 Feb 2006 08:59:58 +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 k1Q8xtsI053532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 26 Feb 2006 11:59:56 +0300 (MSK) (envelope-from os@rsu.ru) Date: Sun, 26 Feb 2006 11:59:55 +0300 (MSK) From: Oleg Sharoiko To: Scott Long In-Reply-To: <43F38E74.6020705@samsco.org> Message-ID: <20060226115730.K774@brain.cc.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <43F38E74.6020705@samsco.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 , John Baldwin 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: Sun, 26 Feb 2006 08:59:59 -0000 On Wed, 15 Feb 2006, Scott Long wrote: SL>This sounds like an interrupt routing problem. The symptoms are similar to SL>others where APIC-routed interrupts don't seem to make it to the active CPUs, SL>depending on whether SMP or HTT is enabled or disabled. Maybe John has some SL>insight here. So is interrupt routing a hardware or a software issue? Taking into account that windows 2003 server works fine with ips I'd say that our particular case is not a hardware issue. If so could you suggest peaces of code should we look at to try solve this problem? -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University.