From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Hardware Error Kernel Mini-Summit Date: Wed, 19 May 2010 00:28:33 +0200 Message-ID: <20100518222832.GJ22675@basil.fritz.box> References: <4BF18995.6070008@redhat.com> <4BF2392A.9040409@jp.fujitsu.com> <4BF2C3D1.10009@redhat.com> <1274204560.17703.82.camel@Joe-Laptop.home> <20100518185305.GA23921@elte.hu> <987664A83D2D224EAE907B061CE93D53C61D1C57@orsmsx505.amr.corp.intel.com> <20100518191802.GG25224@aftab> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "Eric W. Biederman" Cc: Borislav Petkov , "Luck, Tony" , Hidetoshi Seto , Mauro Carvalho Chehab , "Young, Brent" , Linux Kernel Mailing List , Ingo Molnar , Thomas Gleixner , Matt Domsch , Doug Thompson , Joe Perches , Ingo Molnar , "bluesmoke-devel@lists.sourceforge.net" , Andi Kleen , Linux Edac Mailing List List-Id: edac.vger.kernel.org The original motivation to put them somewhere else because I was sick of people reporting them as kernel bugs. But there's more to it now: > If your system isn't broken correctable errors are rare. People look Actually the more memory you have the more common they are. And the trend is to more and more memory. Really to do anything useful with them you need trends and automatic actions (like predictive page offlining) A log isn't really a good format for that. -Andi -- ak@linux.intel.com -- Speaking for myself only.