From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 10 19:26:12 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0046116A4D6 for ; Thu, 10 Feb 2005 19:26:11 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB8DA43D53 for ; Thu, 10 Feb 2005 19:26:11 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 18504 invoked from network); 10 Feb 2005 19:26:11 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for <_pppp@mail.ru>; 10 Feb 2005 19:26:11 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j1AJPewI013930; Thu, 10 Feb 2005 14:25:56 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org, dima <_pppp@mail.ru> Date: Thu, 10 Feb 2005 14:23:47 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <200502101423.47092.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: interrupt routing X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2005 19:26:12 -0000 On Thursday 10 February 2005 09:49 am, dima wrote: > I am preparing a new server for production use. It is dual Opteron Tyan > S2882 motherboard containing 2 1000BaseTX NICs and 2 SCSI controllers > onboard. Running 5.3-RELEASE-p5 (i386). The interrupt assignment performed > by ACPI looks kinda strange: > $ ps -ax > [irq24: bge0 ahd0] > [irq25: bge1 ahd1] > I actually want NICs and SCSI controllers run in different kernel threads. > $ pciconf -lv > ahd0@pci2:6:0: class=0x010000 card=0x005e9005 chip=0x801d9005 rev=0x10 > hdr=0x00 vendor = 'Adaptec Inc' > device = 'AIC-7902B Ultra320 SCSI Controller' > class = mass storage > subclass = SCSI > ahd1@pci2:6:1: class=0x010000 card=0x005e9005 chip=0x801d9005 rev=0x10 > hdr=0x00 vendor = 'Adaptec Inc' > device = 'AIC-7902B Ultra320 SCSI Controller' > class = mass storage > subclass = SCSI > bge0@pci2:9:0: class=0x020000 card=0x164414e4 chip=0x164814e4 rev=0x03 > hdr=0x00 vendor = 'Broadcom Corporation' > device = 'BCM5704 NetXtreme Dual Gigabit Adapter' > class = network > subclass = ethernet > bge1@pci2:9:1: class=0x020000 card=0x164414e4 chip=0x164814e4 rev=0x03 > hdr=0x00 vendor = 'Broadcom Corporation' > device = 'BCM5704 NetXtreme Dual Gigabit Adapter' > class = network > subclass = ethernet > All the devices are assigned IRQ10 in BIOS and I didnt found a way to > change the settings there. I have found a year-old discussion on -current > http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019964.html > about assigning physical IRQ lines to PCI devices; so I want to know if > there is a way to force ACPI assign virtual interrupts a similar way. No. With an APIC (irqs > 16) the interrupt routing is based on how the devices are physically wired up. bge0 and ahd0 are physically hooked up to the same pin on the motherboard and there's nothing FreeBSD can do about that. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org