Re: NMI on shutdown
----Security_Multipart(Mon_Jul_29_04_03_45_2013_291)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sean Bruno <sean_bruno@yahoo.com> wrote
in <1374942794.1431.37.camel@localhost>:
se> :-) I just spent the week looking at something that looks like this on
se> my Dell machines. In my testing the NMI EISA problem seems to be coming
se> from the fact that IPMI pokes at both the ACPI and ISA interfaces to the
se> IPMI controller resulting in an attempt to create /dev/ipmi0
se> and /dev/ipmi1.
se>
se> Somewhere in the recent past (affects 9 as well) the ACPI and ISA IPMI
se> device nodes where children of the same parent and
se> ipmi_isa.c::ipmi_isa_identitfy() would see the ACPI attachment and do
se> nothing. Now the two interfaces have different parents in the device
se> tree.
se>
se> On bce(4) based systems, even if not using IPMI, this seems to
se> crash/confuse older version of the management firmware and yield results
se> similar to what you see.
se>
se> I've just commited a tested fix from Yahoo on this that Peter and I
se> worked out. see svn R 253708
Hmm, in my case the symptom does not depend on ipmi(4) (ipmi.ko was
not loaded). I tried the patch in r253708 on stable/9 in both cases
of loading the ipmi.ko or not loading it, but there was no
difference.
Did NMI happen on you box only when ipmi.ko was loaded?
-- Hiroki
----Security_Multipart(Mon_Jul_29_04_03_45_2013_291)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (FreeBSD)
iEYEABECAAYFAlH1axEACgkQTyzT2CeTzy0YMgCgwf1ADVoX2BnlGqBr0RYTUodQ
1W8AoNHGVYhKPBtMkf5609fRMfs8o5+L
=94SW
-----END PGP SIGNATURE-----
----Security_Multipart(Mon_Jul_29_04_03_45_2013_291)----
討論串 (同標題文章)