From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hardware error reporting [was Re: PCI Error reporting]
Date: Tue, 03 Oct 2006 23:00:33 +0000 [thread overview]
Message-ID: <20061003230033.GA21320@kroah.com> (raw)
In-Reply-To: <20061003152636.GA4381@austin.ibm.com>
On Tue, Oct 03, 2006 at 11:26:54AM -0500, Linas Vepstas wrote:
> On Tue, Oct 03, 2006 at 05:57:20PM +0200, Kay Sievers wrote:
> >
> > 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.
> >
> > 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?
>
> 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.
That is the right approach, using a netlink-like socket. Unfortunatly
the project got killed by the sponsering company due to some crazy
in-house politics and misunderstandings about how Linux kernel
development really works.
Hopefully someone implements this properly someday...
thanks,
greg k-h
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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
prev parent reply other threads:[~2006-10-03 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 15:26 Hardware error reporting [was Re: PCI Error reporting] Linas Vepstas
2006-10-03 15:57 ` Kay Sievers
2006-10-03 16:01 ` Linas Vepstas
2006-10-03 16:26 ` Linas Vepstas
2006-10-03 21:52 ` Kay Sievers
2006-10-03 23:00 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061003230033.GA21320@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).