Re: Fwd: Interrupt Overload

--SlNsYPPA1sYaSN7W
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 07, 2014 at 12:48:16PM -0400, Dutch Ingraham wrote:
> On 06/07/2014 12:04 PM, Vladislav Prodan wrote:
> >=20
> >=20
> > =20
> >  --- Original message ---
> >  From: "Dutch Ingraham" <stoa@gmx.us>
> >  Date: 7 June 2014, 18:33:12
> >  =20
> >=20
> >>
> >> 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.
> >=20
> > After reboot what became timer? :)
> >=20
> > You can change the timer "on the fly", without rebooting the system.
> >=20
> > If LAPIC does not help, then try other timers.
> >=20
> >=20
> > --
> >  Vladislav V. Prodan
> >  System & Network Administrator
> >  support.od.ua
> > =20
> > _______________________________________________
> > freebsd-hackers@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o=
rg"
> >=20
>=20
> 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.
>=20
> 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?

You did not shown _useful_ output of vmstat -i.  Do it when the storm
occurs.  Also, show the pciconf -lvc output on the machine.

--SlNsYPPA1sYaSN7W
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTk1KfAAoJEJDCuSvBvK1B18UP+wWcdB8DAcwXxD+P7pdUG5Ql
5IFRioTm/4T9dgb3/zSVy2i66L5mAY+bIDGC7HOUVffyfkZDC1dzzpKSdE3lIJmm
7YvEV+luXURfOUnj1cvrdmJ91ld4jY0CMBgUvb1EJzylQr080H1Lxfg7KPPVL+Go
XtVgf+l8e8/0MIC3ovZK2Vb9k5YPvP5GIR2Ep+FGac8Zl0XaJ9KTKB4DFgAu1DXq
R9nyTsyHfWg+T4+ongV39SAZmJXvvO0al10wOWNSCembhabaFI1A7B/YwL3l3MOr
yAvHeTaDeJoLHe0Lok7a9FCKTqCmw+3Q8zIxts7iDHXsXbehdTLubBcfF9zboo5t
M5eJ8gYAo01oGX1hkW7n68n5wHwzj8AkgSUk9lVy8zpnz5HEuydz6AK0CFUeEJs7
hlOtcpacBXbMmYuaq8YP1LwfLpkCvWZ4FejUf6+bTdDOr5tJHNeDckKMw4ejJ5O2
QW2gI7IMK+LjZxeBFTJoizQcLs5/Rul5SyuetK+wGLY4HA0s0/X2QY5tBpxRvjeI
an0cNz/vMMCmvS6POXY+HOgWeDOugnrJxr9lbMNarEaZ4qV8pldA+UyRQQHhQTKM
MlwAI7R4VT8sKBOctoKfn3Unf8W5g8uTE5Lm6Yi2jFUfc0nJ0vuiriS37eDVBiQf
A1vlp8oNYZvPQEdjNw2r
=IdXS
-----END PGP SIGNATURE-----

--SlNsYPPA1sYaSN7W--