thank you for the replies. netconsole may be fine during development. But I am looking for a mechanism that can report about exceptions, traps, oops and panic that happened in the system (not all printk output as klogd reports) in long run (say an embedded device in production), so that later, one can check the log file in the flash/eeprom to see those traps/exceptions happened. plz help sunil m On Wed, 23 Feb 2005 11:34:54 +0100, Alexander Nyberg <alexn@xxxxxxxxx> wrote: > > > Is it possible to log oops and panic messages into some file in an > > > eeprom device and do a reset instead of getting it printed on console > > > and hangs? Will the system be stable enough to do so while an > > > oops/panic happens ? > > > > Oopses are already logged into a file through syslog. Panics can't be > > logged into a file because the whole reason for a panic is that there > > is no sane way to continue (i.e.: continueing would create more damage > > than there already is). > > > > > getting those messages into the host machine through the serial > > > console is fine. But is it possible the linux exception handlers ( or > > > panic() function ) call some APIs of my driver so as to write those > > > information into a eeprom device ? > > > > No. The best thing to use is serial console or netconsole. > > To be fair, it's possible but it would require some skilled programming > effort. Easiest to look at netconsole. > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
