Date: Sat, 7 Jun 2014 22:45:59 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Dutch Ingraham <stoa@gmx.us> Cc: freebsd-hackers@freebsd.org Subject: Re: [SOLVED] Re: Fwd: Interrupt Overload Message-ID: <20140607194559.GT3991@kib.kiev.ua> In-Reply-To: <trinity-42b39502-69e6-4d77-8230-a7f710654a49-1402169619685@3capp-mailcom-lxa05> References: <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> <20140607175752.GP3991@kib.kiev.ua> <trinity-7a7ae44c-b0f3-4903-9235-60fc64b981d3-1402165268139@3capp-mailcom-lxa12> <20140607184126.GQ3991@kib.kiev.ua> <trinity-42b39502-69e6-4d77-8230-a7f710654a49-1402169619685@3capp-mailcom-lxa05>
next in thread | previous in thread | raw e-mail | index | archive | help
--asVK9fW/mNnnZXE9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 07, 2014 at 09:33:40PM +0200, Dutch Ingraham wrote: >=20 >=20 > > Sent: Saturday, June 07, 2014 at 2:41 PM > > From: "Konstantin Belousov" <kostikbel@gmail.com> > > To: "Dutch Ingraham" <stoa@gmx.us> > > Cc: freebsd-hackers@freebsd.org > > Subject: Re: Fwd: Interrupt Overload > > > > On Sat, Jun 07, 2014 at 08:21:08PM +0200, Dutch Ingraham wrote: > > >=20 > > >=20 > > > > Sent: Saturday, June 07, 2014 at 1:57 PM > > > > From: "Konstantin Belousov" <kostikbel@gmail.com> > > > > To: "Dutch Ingraham" <stoa@gmx.us> > > > > Cc: freebsd-hackers@freebsd.org > > > > Subject: Re: Fwd: Interrupt Overload > > > > > > > > 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) HP= ET4 (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 sy= stem. > > > > > >=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@f= reebsd.org" > > > > > >=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 l= oad > > > > > averages shown in <top> do also drop proportionally. Interesting= ly, > > > > > 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? > > > >=20 > > > > You did not shown _useful_ output of vmstat -i. Do it when the sto= rm > > > > occurs. Also, show the pciconf -lvc output on the machine. > > > >=20 > > >=20 > > > Sorry - I was entering that output by hand, so truncated what I thoug= ht was not useful. =20 > > > In addition, the storm is always occurring, unless I put the machine = to sleep and then wake-up. > > >=20 > > > Here is the full vmstat -i: > > >=20 > > > dutch:~:# vmstat -i > > > interrupt total rate > > > irq1: atkbd0 48 0 > > > irq0: attimer0 12236927 1178 > > > irq8: atrtc0 146537 14 > > > irq16: uhci0 3362560857 323946 > > > irq18: atapci0+ 19828 1 > > > irq23: uhci3 ehci1 2 0 > > > cpu0:timer 163301 15 > > > irq256: hpet0:t0 4516011 435 > > > irq257: hpet0:t1 83960 8 > > > irq264: em0 31799 3 > > > irq265: hdac0 95 0 > > > irq266: ahci0:ch0 8423 0 > > > irq267: ahci0:ch1 15620 1 > > > cpu1:timer 1229 0 > > > irq274: vgapci0 10041 0 > > > Total 3379794678 325606 > > > dutch:~:# > > >=20 > > > And here is pciconf -lvc: > > >=20 > > > dutch:~:# pciconf -lvc > > > hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x04201028 chip=3D0x2e1080= 86 rev=3D0x03 hdr=3D0x00 > > > vendor =3D 'Intel Corporation' > > > device =3D '4 Series Chipset DRAM Controller' > > > class =3D bridge > > > subclass =3D HOST-PCI > > > cap 09[e0] =3D vendor (length 12) Intel cap 6 version 1 > > > pcib1@pci0:0:1:0: class=3D0x060400 card=3D0x04201028 chip=3D0x2e11808= 6 rev=3D0x03 hdr=3D0x01 > > > vendor =3D 'Intel Corporation' > > > device =3D '4 Series Chipset PCI Express Root Port' > > > class =3D bridge > > > subclass =3D PCI-PCI > > > cap 0d[88] =3D PCI Bridge card=3D0x04201028 > > > cap 01[80] =3D powerspec 3 supports D0 D3 current D0 > > > cap 05[90] =3D MSI supports 1 message=20 > > > cap 10[a0] =3D PCI-Express 2 root port slot max data 128(128) lin= k x0(x16) > > > speed 0.0(5.0) ASPM disabled(L0s) > > > ecap 0002[100] =3D VC 1 max VC0 > > > ecap 0005[140] =3D Root Complex Link Declaration 1 > > > vgapci0@pci0:0:2:0: class=3D0x030000 card=3D0x04201028 chip=3D0x2e128= 086 rev=3D0x03 hdr=3D0x00 > > > vendor =3D 'Intel Corporation' > > > device =3D '4 Series Chipset Integrated Graphics Controller' > > > class =3D display > > > subclass =3D VGA > > > cap 05[90] =3D MSI supports 1 message enabled with 1 message > > > cap 01[d0] =3D powerspec 2 supports D0 D3 current D0 > >=20 > > Try to set the tunable hw.drm.msi to 0 before i915 driver is loaded. > > I.e. the easiest is to set it at loader prompt. If you load driver > > by starting Xorg, then kenv hw.drm.msi=3D0 would be enough. > >=20 > > Either way, helped it or not, post the vmstat -i output while the Xorg > > is running. > >=20 >=20 > BEAUTIFUL!! Knocked the uhci interrupts to normal. Here is the >vmstat = -i> > with X running and hw.drm.msi=3D0 set: >=20 > dutch@dutch:~ % vmstat -i > interrupt total rate > irq1: atkbd0 48 0 > irq16: uhci0+ 167 1 > irq18: atapci0+ 344 3 > irq23: uhci3 ehci1 2 0 > irq256: hpet0:t0 10675 111 > irq257: hpet0:t1 5897 61 > irq264: em0 341 3 > irq265: hdac0 95 0 > irq266: ahci0:ch0 4274 44 > irq267: ahci0:ch1 155 1 > Total 21998 229 > dutch@dutch:~ % >=20 > HPETs are a little high, but overall 1000% better. I have added > to my /boot/loader.conf. Why do you think that HPET is 'a little high' ? It is down from the hz, which is probably 1024 on your machine, so it is a little low. Still, I do not believe that the above vmstat -i is from the running Xorg session. What interrupt i915 gfx uses, it probably shared on irq16 ? If so, it cannot be total 167 interrupts for the started X session, even if dumbed down to X running a single xterm. >=20 > I see where this was discussed back in the 7.2R release notes, but > I would have never found it. Many thanks for your help. There is some unpublished errata for G45/GM45 chipsets where display interrupts are reported by legacy method even if the MSI is enabled. I think it is somehow related to the motherboard or BIOS layout since the situation is very rare. --asVK9fW/mNnnZXE9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTk2v2AAoJEJDCuSvBvK1BeN0P+gMcH9xG/LYV6s3DsPJcVtJo L8mayS7VZdNrcyp7Cqykpxraz7NTjJc1KAiyInz2pM8XPimEsvyNx2rHd42+UqVk XjnUPVS9HheUlwCqRahOtFlOcyfEGLjx2oKMnLYHmtmhmUl/Jxjlg0BiOVTAoxrz ZU55FG0QXGaakh+Svs1CoqIg1EsJ58qD7+eJcPDnEDJU255ppQgHKBvaHlvWj2J0 yYN+gaKaNlD2Wf0hE801Pdoxa2oiOUMvHVFRF8VtdJCJLDhdbyDpoPnufeZ56dQM 40d7pXqpBeGpEnF/7LpADFnuT6gwqbii65K7U3QO8yHHbiCUMepPwoL6h2JQ9vSt uuXaYLFIvMrTmgB4tNnySH13Kg8zDnfto/cB2b4xa8edLPbGbUPHVtc6WtDsyQkY xVkygs1DY6GFGY6MXZfO75yPRtN0jfiz+opQskQnzVaFSNXujfTXmiIz3PS0xrd1 XlYTX6DmhvltijjDPO6HoTzZnFftgpr5nrjBg/uucguGJ5N18dTLrY2t1dIjXvT6 o8lVQJZuZMkHGX1AMaCCa6LPqS/e4arqRCwOY8I1sKYi0qZ3IeC5FaIXoZGQXour OaW09/H5da5wetsSelI48CYA4+z8pVn21PYSmoa89sdiyEpe1vRYravaG0cgktH1 RYpZ0/T7UKzrWFuJPvcS =EnO/ -----END PGP SIGNATURE----- --asVK9fW/mNnnZXE9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140607194559.GT3991>