Date: Sat, 7 Jun 2014 12:55:32 -0400 From: Adrian Chadd <adrian@freebsd.org> To: Dutch Ingraham <stoa@gmx.us> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Fwd: Interrupt Overload Message-ID: <CAJ-VmomDiuG2t7pT2cJ5XO%2BZWyjzcgGx-gnZ_ei3NaaigFGtUw@mail.gmail.com> In-Reply-To: <53934250.1090403@gmx.us> References: <538A3432.5010303@gmx.us> <53930E19.8090603@gmx.us> <53931963.4040604@selasky.org> <53932314.6010108@gmx.us> <1402153691.709851721.u6k6kkkk@frv35.fwdcdn.com> <53933110.8060300@gmx.us> <1402157083.156846225.m95e69ke@frv35.fwdcdn.com> <53934250.1090403@gmx.us>
next in thread | previous in thread | raw e-mail | index | archive | help
It sounds much more like some unhandled interrupt status bit/condition somewhere. It's possible that putting things to sleep clears that condition. -a On 7 June 2014 12:48, Dutch Ingraham <stoa@gmx.us> wrote: > On 06/07/2014 12:04 PM, Vladislav Prodan wrote: >> >> >> >> --- Original message --- >> From: "Dutch Ingraham" <stoa@gmx.us> >> Date: 7 June 2014, 18:33:12 >> >> >>> >>> Thanks for the response. >>> >>> The output you requested: >>> >>> kern.eventtimer.choice: HPET1 (440) HPET2 (440) HPET3 (440) HPET4 (440) >>> HPET5 (440) HPET6 (440) LAPIC (400) i8254 (100) RTC (0) >>> >>> kern.eventtimer.choice: HPET (did not specify 1, 2, etc.) >>> >>> I also changed the type of timer to LAPIC and rebooted; there was no >>> appreciable change in the interrupt activity. >> >> After reboot what became timer? :) >> >> You can change the timer "on the fly", without rebooting the system. >> >> If LAPIC does not help, then try other timers. >> >> >> -- >> Vladislav V. Prodan >> System & Network Administrator >> support.od.ua >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > > You're right, it is not persistent. I changed to each different event > timer and the only one that made a difference was the i8254; that > dropped the cpu load from 30% to 10-12%. Much better, but still of > course not acceptable for a Core II-Duo running at 3.0GHz. The load > averages shown in <top> do also drop proportionally. Interestingly, > though, <systat -vmstat> shows the same interrupt rate - 325K/sec. > > What do you make of the fact that when I suspend with <<acpiconf -s 3> > and then wake-up, everything is absolutely normal, regardless of event > timer type? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomDiuG2t7pT2cJ5XO%2BZWyjzcgGx-gnZ_ei3NaaigFGtUw>