From owner-freebsd-current@FreeBSD.ORG Mon May 19 13:15:21 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 3F16D37B401 for ; Mon, 19 May 2003 13:15:21 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FE2643FAF for ; Mon, 19 May 2003 13:15:20 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h4JKFGXi031148; Mon, 19 May 2003 15:15:16 -0500 (CDT) (envelope-from dan) Date: Mon, 19 May 2003 15:15:16 -0500 From: Dan Nelson To: Lars Eggert Message-ID: <20030519201516.GF39543@dan.emsphone.com> References: <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> <20030519200002.GE39543@dan.emsphone.com> <3EC939B1.8020606@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EC939B1.8020606@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:15:21 -0000 In the last episode (May 19), Lars Eggert said: > Dan Nelson wrote: > >In the last episode (May 19), Lars Eggert said: > >> > >>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: > > > >You sure you have acpi loaded? It shows up for me: > > > >$ ps ax | grep acpi0 > > 22 ?? WL 0:00.00 (irq9: acpi0) > > I'm pretty sure I do - maybe acpi irq handling is different with an SMP > kernel? I'm running SMP also (May 13 kernel). > [larse@nik: ~] ps ax | grep acpi > 5 ?? IL 0:00.00 (acpi_task0) > 6 ?? IL 0:00.00 (acpi_task1) > 7 ?? IL 0:00.00 (acpi_task2) > 78714 p4 LV+ 0:00.00 grep acpi (tcsh) $ ps ax | grep acpi 5 ?? IL 0:00.00 (acpi_task0) 6 ?? IL 0:00.00 (acpi_task1) 7 ?? IL 0:00.00 (acpi_task2) 20 ?? WL 0:00.00 (swi6: acpitaskq) 22 ?? WL 0:00.00 (irq9: acpi0) Unfortunately, I don't have enough devices in my system for the BIOS to have to share IRQs. > [larse@nik: ~] kldstat | grep acpi > 46 1 0xc068b000 48514 acpi.ko I don't use modules, though. Everything's linked directly into the kernel. I doubt that makes a difference. -- Dan Nelson dnelson@allantgroup.com