Date: Mon, 19 May 2003 15:15:16 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Lars Eggert <larse@ISI.EDU> Cc: current@freebsd.org Subject: Re: Interrupt latency problems Message-ID: <20030519201516.GF39543@dan.emsphone.com> In-Reply-To: <3EC939B1.8020606@isi.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519201516.GF39543>