Date: Sat, 27 Jul 2013 09:33:14 -0700 From: Sean Bruno <sean_bruno@yahoo.com> To: Hiroki Sato <hrs@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: NMI on shutdown Message-ID: <1374942794.1431.37.camel@localhost> In-Reply-To: <20130727.130641.1045344958497890348.hrs@allbsd.org> References: <20130727.130641.1045344958497890348.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ucjGMHAx35DlMpGLoNMl Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sat, 2013-07-27 at 13:06 +0900, Hiroki Sato wrote: > Hi, >=20 > The following log messages are displayed on a box where I am testing > stable/9. It occurs only when trying to shutdown the box: >=20 > | Waiting (max 60 seconds) for system process `vnlru' to stop...done > | Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > | Waiting (max 60 seconds) for system process `syncer' to stop... > | Syncing disks, vnodes remaining...2 2 0 0 done > | All buffers synced. > | Uptime: 8d2h4m58s > | NMI ISA 30, EISA 0 > | NMI ISA 20, EISA 0 > | NMI ... going to debugger > | NMI ... going to debugger > | NMI ISA 20, EISA 0 > | NMI ISA 30, EISA 0 > | NMI ... going to debugger > | NMI ... going to debugger > | NMI ISA 20, EISA 0 > ... > | timeout stopping cpus > | [ thread pid 11 tid 100016 ] > | Stopped at acpi_cpu_c1+0x6: leave > | db> timeout stopping cpus > | timeout stopping cpus > | [ thread pid 11 tid 100015 ] > | Stopped at acpi_cpu_c1+0x6: leave > | db> timeout stopping cpus > | timeout stopping cpus >=20 > Once these are displayed, a power cycle is required to recover. > Shutdown sometimes works, and sometimes not. DDB prompt does not > work because it does not accept entered characters properly. And, > this symptom seems not specific to stable/9. >=20 > This may be a hardware specific issue, but where should I start to > debug this from? >=20 > -- Hiroki :-) I just spent the week looking at something that looks like this on my Dell machines. In my testing the NMI EISA problem seems to be coming from the fact that IPMI pokes at both the ACPI and ISA interfaces to the IPMI controller resulting in an attempt to create /dev/ipmi0 and /dev/ipmi1. Somewhere in the recent past (affects 9 as well) the ACPI and ISA IPMI device nodes where children of the same parent and ipmi_isa.c::ipmi_isa_identitfy() would see the ACPI attachment and do nothing. Now the two interfaces have different parents in the device tree. On bce(4) based systems, even if not using IPMI, this seems to crash/confuse older version of the management firmware and yield results similar to what you see. I've just commited a tested fix from Yahoo on this that Peter and I worked out. see svn R 253708 Sean --=-ucjGMHAx35DlMpGLoNMl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJR8/ZDAAoJEBkJRdwI6BaHtD4H/2oEGpm8QStpMdpVPjweyAZ8 n1hONZTt2HDU8jaqfwlZ5FWhOGWhnp+Cwze57rQ8xKAzr+MCSMuhFtTICiMfkmJ+ PQZlRXMEC7H1D1SHA2EU3szdYSMcKuRbw+cFZO3GdLucd1vIbxj6grvF5tYR9c0q Sw34CIHoHCFtGnJLWXgEmVScdsWsTj/bKkkyou3swUyVhqomKSGRCqQZnEhWAuon eC+OjoPXR4k1CUWhAIYtAJVVBTgTmIcW/R4sodT56WcOeiorA4/5+JaOfrupSqFP FP2uLuMNw6h9VWRKYNuhyF3KMetFYUvj/Jd47zdIk6p/2KT1TDiwv8iC78jal9U= =NjOl -----END PGP SIGNATURE----- --=-ucjGMHAx35DlMpGLoNMl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1374942794.1431.37.camel>