From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 03 Oct 2006 15:57:20 +0000 Subject: Re: Hardware error reporting [was Re: PCI Error reporting] Message-Id: <1159891040.3430.36.camel@localhost> 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, 2006-10-03 at 10:26 -0500, Linas Vepstas wrote: > > I am the maintainer of the KDE 'task manager' equivalent (kde system > > guard). I was discussing with someone in the UK about telling the user > > about PCI bus errors. The idea would be to inform the user that their > > soundcard etc is no longer working etc. 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. > Anyway, userspace gets messages from the kernel via "hald" > (hardware abstraction layer daemon) and the sbus(??)I forget > what its called, the system message bus. These two are plugged=20 > into the udev infrastructure. Udev listens to kernel messages on the kernel netlink socket and handles the "low level" stuff like module loading, device node creation, running small device initialization programs. After udev is finished, it sends the event to HAL. HAL classifies the device and adds the device to its own device tree. This list can be queried over DBus by applications, mostly desktop software. But unfortunately, none of these software pieces are useful for error reporting today, cause you just don't get any useful data out of the kernel. It may be nice to integrate a kernel error classification/reporting system into HAL, but we don't have such a thing. And just in case: using the driver-core event-infrastucture (udev) is the totally wrong approach to relay kernel errors to userspace. Thanks, Kay ------------------------------------------------------------------------- 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