Re: [evlog-dev] alternate event logging proposal

[Jeff Garzik]

Daniel E. F. Stekloff wrote:
> I agree with you that there needs to be a strategy for what is logged by a 
> driver and how it is logged. We believe log analysis is an essential part of 
> diagnosing errors. Log messages, when generated consistently, could indicate 
> what drivers were loaded, when they were loaded, what their current version 
> is, and what errors they have encountered. How the messages are formatted, 
> whether they follow certain rules, can greatly aid User Space diagnostic 
> applications. 
> 
> We propose standardizing what should be logged and how those log messages 
> should look.

[snip]

> Any comments?

I agree with the generalities... I am looking for something far more 
specific, though.

My point in the second half of my proposal message was trying to drive 
home the point that IBM doesn't appear to know, at this time, what the 
diagnostic messages the 8139too net driver should output.  Or the 
aic7xxxx scsi driver.  Or the piix ATA driver.

And until IBM knows those things, I cannot see how any proposal can be 
put forward.  _what data_ should be logged?  "useful data" is not an 
answer.  "eeprom checksum failure, with failed checksum value" is an 
answer.  If IBM does not know these things, it is putting forward a 
solution when the problem has not clearly been examined or even defined.

I want all my net drivers to log useful data.  I also want world peace. 
  The devil is in the details.

	Jeff