lkcd
[Top] [All Lists]

lkcd & I2c

To: "'lkcd@xxxxxxxxxxx'" <lkcd@xxxxxxxxxxx>
Subject: lkcd & I2c
From: "Scott, Colin" <colin.scott@xxxxxxxxxx>
Date: Fri, 9 Mar 2001 11:53:13 -0500
Cc: "'goemon@xxxxxxxxx'" <goemon@xxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
Hi,

Are there any plans to have lkcd dump the system hardware and environment
status info using the I2c protocol? The current 2.4.x kernels already have
I2c code and drivers. Maybe they could be used to get the hardware and
environment status info at the exact time of a crash or kernel panic? It
would be a good idea to be able to eliminate for example CPU/Chipset
overheating problems or memory parity errors as the cause of a crash before
starting a painstaking investigation into what might actually be bug free
kernel code. This code should be added to lckd because the syslog daemon
would probably not get chance to report most hardware errors before the
system dumps memory and reboots. I would also like to see ECC memory status
messages if bad ECC memory was the cause of the system panic. Michael
O'Reilly has written some code to do ECC error reporting to the kernel
logfile. Is there any chance that this code could be merged into lkcd? See
http://www.anime.net/~goemon/linux-ecc/ for details. The addition of
hardware failure reporting code to lkcd could make Linux into a more
reliable and more Highly Available UNIX variant by allowing us to identify
and replace bad hardware in the system and would take Linux one more step
closer to becoming a mature and reliable OS.


Colin Scott
Senior Technical Specialist
Schering-Plough Corp.

Disclaimer: This email does not represent the opinions or interests of
Schering-Plough Corp.

<Prev in Thread] Current Thread [Next in Thread>