Date: Sun, 11 May 2003 22:20:38 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Paul Richards <paul@freebsd-services.com> Cc: current@freebsd.org Subject: Re: Interrupt latency problems Message-ID: <16063.1270.712211.263308@curly.cs.duke.edu> In-Reply-To: <1052703871.4921.146.camel@cf.freebsd-services.com> References: <22333.1052574519@critter.freebsd.dk> <20030511.134504.85393710.imp@bsdimp.com> <1052684139.4921.3.camel@cf.freebsd-services.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Richards writes: > > As a further datapoint to my last email: > > 20 ?? WL 5:16.38 (irq9: fxp0 acpi0) > > I'll see if I can shift the interrupts around in the bios but I don't > think I can since fxp is onboard. I think you might be able to reserve IRQ 9 for some legacy device or something in the BIOS. > Perhaps acpi doesn't do anything to check whether the interrupt belongs > to it or not and so when an fxp interrupt arrives the acpi handler gets > called. That's a good theory. I think you might have something there. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16063.1270.712211.263308>