From mboxrd@z Thu Jan 1 00:00:00 1970 From: linas@austin.ibm.com (Linas Vepstas) Date: Tue, 03 Oct 2006 16:26:54 +0000 Subject: Re: Hardware error reporting [was Re: PCI Error reporting] Message-Id: <20061003162654.GD4381@austin.ibm.com> List-Id: References: <20061003152636.GA4381@austin.ibm.com> In-Reply-To: <20061003152636.GA4381@austin.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Tue, Oct 03, 2006 at 05:57:20PM +0200, Kay Sievers wrote: >=20 > Error classification/reporting is a completely missing piece in Linux. > Today there is no sane example of error reporting in the Linux kernel. > Printk and friends are totally useless for anything else than the geek > in front of the computer. Until the kernel gets a sane error > classification/reporting infrastructure, it's impossible to solve such a > problem. >=20 > And just in case: using the driver-core event-infrastucture (udev) is > the totally wrong approach to relay kernel errors to userspace. So what's the right approach?=20 Historically, I notice there was an attempt called "evlog" (http://evlog.sourceforge.net/) which bombed out; the latest patches were to 2.6.4 from 2005. --linas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel