From owner-freebsd-stable@FreeBSD.ORG  Sun Aug 14 05:54:54 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 9598116A41F
	for <stable@freebsd.org>; Sun, 14 Aug 2005 05:54:54 +0000 (GMT)
	(envelope-from bfoz@bfoz.net)
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.76.28])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 43C5743D55
	for <stable@freebsd.org>; Sun, 14 Aug 2005 05:54:54 +0000 (GMT)
	(envelope-from bfoz@bfoz.net)
Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233])
	by comcast.net (sccrmhc13) with ESMTP
	id <2005081405545301300l4uiee>; Sun, 14 Aug 2005 05:54:53 +0000
Message-ID: <42FEDCAB.2040904@bfoz.net>
Date: Sat, 13 Aug 2005 22:54:51 -0700
From: Brandon Fosdick <bfoz@bfoz.net>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Darren Pilgrim <dmp@bitfreak.org>
References: <001701c5a092$6eb78f00$642a15ac@SMILEY>
In-Reply-To: <001701c5a092$6eb78f00$642a15ac@SMILEY>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stable@freebsd.org
Subject: Re: IRQ conflict between twa0 and skc0
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2005 05:54:54 -0000

Darren Pilgrim wrote:
> Try switching slots with the RAID and video cards.  It's silly, but then
> so is PCI interrupt routing.

Unbelievable. Who ever wrote the PCI spec should have been shot.

I switched the cards and now the network card is sharing an interrupt with the video card, but neither seems to mind. More importantly it isn't sharing with the raid card and they all appear to be happy.

Thanks, that was a big help.