Date: Wed, 10 Mar 2004 13:01:24 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@freebsd.org Cc: current@freebsd.org Subject: Re: diagnosing interrupt storms? Message-ID: <200403101301.24106.jhb@FreeBSD.org> In-Reply-To: <20040309181938.GP56622@elvis.mu.org> References: <20040309071912.GM56622@elvis.mu.org> <20040309095540.U69332@carver.gumbysoft.com> <20040309181938.GP56622@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 09 March 2004 01:19 pm, Alfred Perlstein wrote: > * Doug White <dwhite@gumbysoft.com> [040309 09:57] wrote: > > On Mon, 8 Mar 2004, Alfred Perlstein wrote: > > > At a certain point after booting my SMP 5-current box gets all > > > weird, typically I see 50%+ time spent in interrupt. If I run "top > > > -S" I typically see one of the ithreads using 50% cpu. > > > > > > I'm trying to figure out what it's doing, what has gone wrong etc. > > > > > > Are there any sysctls to look at or things I can do to diagnose > > > this? > > > > vmstat -i is useful for figuring out exactly which interrupt is storming, > > although the ithread might hint it too. > > > > Which one is it? > > It's typically been em (intel gigE) or the sound interrupt. Is it on irq 20 and shared with acpi0? Alternatively, it could be misrouted. Are you using X and drm? Many BIOSs seem to forget that VGA devices can have IRQs and don't provide interrupt routing information for them, so drm0 gets the wrong IRQ and the correct IRQ gets a storm when the drm0 device interrupts. I guess window doesn't use the VGA IRQ in its graphics drivers since BIOS writers seem to only care about what makes Windows works and tend to demonstrate a stricking lack of proficiency in English when it comes to written standards such as ACPI, etc. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403101301.24106.jhb>