Date: Sat, 07 Jun 2014 19:04:43 +0300 From: Vladislav Prodan <universite@ukr.net> To: Dutch Ingraham <stoa@gmx.us> Cc: freebsd-hackers@freebsd.org Subject: Re[2]: Fwd: Interrupt Overload Message-ID: <1402157083.156846225.m95e69ke@frv35.fwdcdn.com> In-Reply-To: <53933110.8060300@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1402157083.156846225.m95e69ke>