From owner-freebsd-current@FreeBSD.ORG Mon May 19 13:00:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C4D037B401 for ; Mon, 19 May 2003 13:00:26 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C31CF43FB1 for ; Mon, 19 May 2003 13:00:25 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h4JK02dq074923; Mon, 19 May 2003 15:00:02 -0500 (CDT) (envelope-from dan) Date: Mon, 19 May 2003 15:00:02 -0500 From: Dan Nelson To: Lars Eggert Message-ID: <20030519200002.GE39543@dan.emsphone.com> References: <20030511.143231.133432780.imp@bsdimp.com> <1052692357.4921.128.camel@cf.freebsd-services.com> <16062.59918.302092.929640@curly.cs.duke.edu> <1052703871.4921.146.camel@cf.freebsd-services.com> <16063.38255.961273.900146@grasshopper.cs.duke.edu> <20030512124753.GA48753@survey.codeburst.net> <16063.39366.930707.980678@grasshopper.cs.duke.edu> <20030512130949.GB48440@survey.codeburst.net> <1053372251.815.50.camel@cf.freebsd-services.com> <3EC93331.7090004@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EC93331.7090004@isi.edu> X-OS: FreeBSD 5.1-BETA X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: Andrew Gallatin cc: current@freebsd.org Subject: Re: Interrupt latency problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 20:00:26 -0000 In the last episode (May 19), Lars Eggert said: > Paul Richards wrote: > > I'm also not sure why a lot more people aren't seeing this, unless > > my motherboard is odd in sharing the acpi interrupt with a pci > > slot. > > I tried to see if this is the case on my SMP board, but I don't seem > to have acpi attached to any interrupt: > > [root@nik: ~] ps -axg | grep irq > 24 ?? WL 0:00.00 (irq18: mpt0) > 25 ?? WL 0:19.30 (irq19: em0 mpt1) > 26 ?? WL 0:00.00 (irq16: xl0 uhci1) > 27 ?? WL 1:57.07 (irq17: fwohci0 drm0) > 28 ?? WL 1:09.27 (irq13: em1 ichsmb0) > 29 ?? WL 0:00.02 (irq20: pcm0) > 30 ?? WL 0:02.19 (irq2: uhci0 bktr0) > 31 ?? WL 0:02.84 (irq14: ata0) > 32 ?? WL 0:00.00 (irq15: ata1) > 36 ?? WL 0:00.00 (irq6: fdc0) > 37 ?? WL 0:00.00 (irq1: atkbd0) > > Is this the right way to check for this? You sure you have acpi loaded? It shows up for me: $ ps ax | grep acpi0 22 ?? WL 0:00.00 (irq9: acpi0) Maybe the attach message to acpi should print the IRQ it's using. All I get in dmesg is "acpi0: on motherboard". -- Dan Nelson dnelson@allantgroup.com