Date: Tue, 9 Mar 2004 03:40:02 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: Scott Long <scottl@freebsd.org> Cc: current@freebsd.org Subject: Re: diagnosing interrupt storms? Message-ID: <20040309114002.GN56622@elvis.mu.org> In-Reply-To: <20040309010921.Y61788@pooker.samsco.home> References: <20040309071912.GM56622@elvis.mu.org> <20040309010921.Y61788@pooker.samsco.home>
next in thread | previous in thread | raw e-mail | index | archive | help
* Scott Long <scottl@freebsd.org> [040309 00:08] 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? > > > > (also I my laptop still can't boot with top-of-the-tree current) :( > > > > A dmesg here would help, of course. You might have a similar problem as > me, where the SMI interrupt is misconfigured as active-low instead of > active-high, so it storms the system. Does disabling ACPI make a > difference? Since it's SMP, does disabling APIC (and thus turning it into > UP) make a difference? dmesg doesn't report anything out of the ordinary. I will try your suggestions the next time I get wedged. thank you, -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040309114002.GN56622>