From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 7 Oct 2015 16:41:56 +0200 From: Gilles Chanteperdrix Message-ID: <20151007144156.GC30140@hermes.click-hack.org> References: <56139C8B.3060509@control.lth.se> <20151006192323.GB30765@hermes.click-hack.org> <5614C8E3.5090809@sigmatek.at> <5614D22A.8030203@sigmatek.at> <5615108A.6070001@control.lth.se> <20151007124107.GB30140@hermes.click-hack.org> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: Subject: Re: [Xenomai] Problems disabling SMI interrupts on MSI H87-G43 motherboard List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anders Blomdell Cc: Xenomai@xenomai.org On Wed, Oct 07, 2015 at 03:03:25PM +0200, Anders Blomdell wrote: >=20 >=20 > On October 7, 2015 2:41:07 PM GMT+02:00, Gilles Chanteperdrix wrote: > >On Wed, Oct 07, 2015 at 02:31:06PM +0200, Anders Blomdell wrote: > >> On 2015-10-07 10:04, Johann Obermayr wrote: > >> > Am 07.10.2015 um 09:25 schrieb Johann Obermayr: > >> >> Am 06.10.2015 um 21:23 schrieb Gilles Chanteperdrix: > >> >>> On Tue, Oct 06, 2015 at 12:03:55PM +0200, Anders Blomdell wrote: > >> >>>> Hi > >> >>>> > >> >>>> I have problems disabling SMI-interrupts on "MSI H87-G43 > >motherboard" (http://www.msi.com/product/mb/H87-G43.html) > >> >>>> > >> >>>> This is what msi.c says at bootup (after attached patch is > >applied): > >> >>>> > >> >>>> kernel: [Xenomai] SMI workaround failed! (1830: 1 & ~1 -> 1) > >> >>>> > >> >>>> and this is what lspci says: > >> >>>> > >> >>>> > >> >>>> Anybody who has a good idea how to fix this? > >> >>> You should first check that the way smi.c retrieves the address > >of > >> >>> the SMI_EN register is still valid for your chipset. If it is, > >then > >> >>> try fiddling with the BIOS settings to see if some setting can > >> >>> disable generation of SMIs. If unsuccessful, you can try > >contacting > >> >>> the motherboard support to see if they have any advice. > >> >>> > >> >> On new Mainboards, you can't disable SMI. > >> >> Because this is a security problem, so SMI is locked by BIOS. > >> >> There are some registery on the mainboard chipset, hat lock the > >SMI register. > >> >> So you can't disable the SMI. > >> >> We also had this trouble, and we get a own BIOS with disabled SMI. > >> >> > >> >> Regards > >> >> Johann > >> >> > >> >> _______________________________________________ > >> >> Xenomai mailing list > >> >> Xenomai@xenomai.org > >> >> http://xenomai.org/mailman/listinfo/xenomai > >> >> > >> > Found this: > >> >=20 > >> > GEN_PMCON_1=97General PM Configuration 1 Register (PM=97D31:F0) > >> > Offset Address: A0h Attribute: R/W, RO, R/WO > >> > Default Value: 0000h Size: 16-bit > >> > Lockable: No Usage: ACPI, Legacy > >> > Power Well: Core > >> >=20 > >> > Bit 4: SMI_LOCK =97 R/WO. When this bit is set, writes to the > >GLB_SMI_EN bit (PMBASE > >> > + 30h, bit 0) will have no effect. Once the SMI_LOCK bit is set, > >writes of 0 to > >> > SMI_LOCK bit will have no effect (that is, once set, this bit can > >only be cleared by > >> > PLTRST#). > >> >=20 > >>=20 > >> Thanks everybody, seems like I have to give up on that motherboard: > >>=20 > >> 1. Nothing found to disable in the BIOS > >> 2. Disabling all sourcecs with smictrl > >(git://git.kiszka.org/smictrl.git) > >> still gives high latencies with RTNet (+1.5 milliseconds).=20 > >> 3. latency test does not show anything suspicious, so it might > >> be some other issue. > >>=20 > >> Anybody that has a suggestion on a recent motherboard that has been > >used with > >> RTNet and showing good results? > > > >If the issue is with RTNet, does not it make more sense to find the > >RTNet issue than to change motherboard? If you are able to detect a > >high latency, can you not trigger a trace from the I-pipe tracer? >=20 > Well, same kernel identical ethernetcard on motherboard without SMI, work= s flawlessly (network jitter in 30 ms range). >=20 > BTW: only the RTNet drivers, raw ethernet. Using the I-pipe tracer and user-space msr-tools, you should be able to confirm whether the issue is due to SMIs. --=20 Gilles. https://click-hack.org