From owner-freebsd-stable@FreeBSD.ORG Mon Aug 21 13:27:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C07F16A4E1 for ; Mon, 21 Aug 2006 13:27:46 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E59743D53 for ; Mon, 21 Aug 2006 13:27:45 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id k7LDRi0l008779 for ; Mon, 21 Aug 2006 15:27:44 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k7LDRha9048298; Mon, 21 Aug 2006 15:27:43 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k7LDRhuj048297; Mon, 21 Aug 2006 15:27:43 +0200 (CEST) (envelope-from ry93) Date: Mon, 21 Aug 2006 15:27:43 +0200 From: "Patrick M. Hausen" To: Matt Dawson Message-ID: <20060821132743.GC45736@hugo10.ka.punkt.de> References: <20060821120052.0B25816A526@hub.freebsd.org> <200608211414.16731.matt@chronos.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200608211414.16731.matt@chronos.org.uk> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: ATA problems again ... general problem of ICH7 or ATA? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 13:27:46 -0000 Hello! On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote: > FWIW, the problem takes *far* longer to rear its head when the SATA controller > has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad > Thing [TM] as the BIOS simply maps the INT to a single IRQ and both devices > end up sharing it. Now tranfer a large file over the network and watch the > ensuing hilarity) and it happens at least every couple of days. Now, with the > slot shared with the SATA controller empty, I have six days uptime since the > last event, which means I'm probably due one any time now. FWIW - here's the setup of my systems that have not shown the problem so far: Device IRQ ------ --- em0 16 em1 17 uhci0 23 uhci1 19 uhci2 18 uhci3 16 ehci0 23 fxp0 16 atapci1 19 This is the SATA300 controller Is there a method to force the controller to share its IRQ with, say, em0 for testing? Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de