Date: Tue, 18 Oct 2011 16:05:02 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable <freebsd-stable@FreeBSD.org> Subject: Re: Interpreting MCA error output Message-ID: <4E9D797E.6000703@FreeBSD.org> In-Reply-To: <20111018113302.GA14363@icarus.home.lan> References: <CAFU734y3WsVFTpnGoGfbPH4vVBnoz8f=qGvYS4c%2BLya8PFQP_A@mail.gmail.com> <20111001102327.GA37434@icarus.home.lan> <CAFU734xHMugfW%2BZcO93OPqUEhJshYn-k%2B%2B3aGmcDVvGZVQ=s%2BQ@mail.gmail.com> <20111018071941.GA9482@icarus.home.lan> <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> <20111018113302.GA14363@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
on 18/10/2011 14:33 Jeremy Chadwick said the following: > Why? Most MCEs on FreeBSD will panic the machine. Incorrect. Correctable MCEs should not panic a machine. Uncorrectable should. > I would need to go > through the MCA code to see what all gets handled elegantly, Please do. > but I > imagine there isn't much. Please defer your imagination. > Also, isn't devd for device removal/insertions? Not only. It might have started like that, but now it is almost a generic mechanism for kernel to userland notifications (e.g. ACPI events). > This would be using > devd for something it isn't intended for. I guess I have "moral > objections" to it. What you're really wanting is Solaris's fmd(1m) > daemon, which I believe is also tied heavily into Solaris's smf(5) > architecture. > > http://download.oracle.com/docs/cd/E19963-01/html/821-1462/fmd-1m.html -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E9D797E.6000703>