Date: Mon, 12 May 2003 08:55:34 -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.39366.930707.980678@grasshopper.cs.duke.edu> In-Reply-To: <20030512124753.GA48753@survey.codeburst.net> 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> <16063.38255.961273.900146@grasshopper.cs.duke.edu> <20030512124753.GA48753@survey.codeburst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Richards writes: > > I tried shifting the irq around last night, the bios does support this. > I definitely think there's something to this theory, when I put it on > irq 10 the problem got a whole lots worse to the point that the machine > couldn't be used and I had to reboot it (just error messages streaming > past on the console). > > Unfortunately, I don't know what else was on irq10 at the time since > they move around when I change the bios settings. > > I'm continuing to poke around to find out exactly what's causing > what.... I have this vague memory that the acpi always uses irq 9. Perhaps you inadvertently moved something else which generates more interrupts onto irq 9.. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16063.39366.930707.980678>