From owner-freebsd-stable@FreeBSD.ORG Mon Aug 21 13:39:04 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 70E9816A4DD for ; Mon, 21 Aug 2006 13:39:04 +0000 (UTC) (envelope-from dom@goodforbusiness.co.uk) Received: from mailhost.graphdata.co.uk (mailhost.graphdata.co.uk [195.12.22.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D631D43D76 for ; Mon, 21 Aug 2006 13:39:03 +0000 (GMT) (envelope-from dom@goodforbusiness.co.uk) Received: from localhost (localhost [127.0.0.1]) by mailhost.graphdata.co.uk (Postfix) with ESMTP id 3403E11402F; Mon, 21 Aug 2006 14:39:02 +0100 (BST) X-Virus-Scanned: amavisd-new at graphdata.co.uk Received: from mailhost.graphdata.co.uk ([127.0.0.1]) by localhost (mailhost.graphdata.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvllIMK7NKg8; Mon, 21 Aug 2006 14:38:57 +0100 (BST) Received: from [192.168.0.86] (gdc083.internal.graphdata.co.uk [192.168.0.86]) by mailhost.graphdata.co.uk (Postfix) with ESMTP id DF281114026; Mon, 21 Aug 2006 14:38:57 +0100 (BST) Message-ID: <44E9B771.3080604@goodforbusiness.co.uk> Date: Mon, 21 Aug 2006 14:38:57 +0100 From: Dominic Marks User-Agent: Thunderbird 1.5.0.5 (X11/20060809) MIME-Version: 1.0 To: "Patrick M. Hausen" , freebsd-stable@freebsd.org References: <20060821120052.0B25816A526@hub.freebsd.org> <200608211414.16731.matt@chronos.org.uk> <20060821132743.GC45736@hugo10.ka.punkt.de> In-Reply-To: <20060821132743.GC45736@hugo10.ka.punkt.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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:39:04 -0000 Patrick M. Hausen wrote: > 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? You can use device.hints(5) to do this. I have the following in mine to force a RAID card and Sound card to share IRQ 17. You need to modify it to suit your environment. hw.pci3.13.INTA.irq="17" The `13' value is the device number, you can find this in dmesg, same for pciN. HTH, Dominic > Regards, > > Patrick M. Hausen > Leiter Netzwerke und Sicherheit