Reading linux boot args
How to read the reason for Kernel reboot? Currently i am using __setup("warmboot=",myfunc) But it looks like i can use this on only one time. If i do this for two times in two drivers only one guy is getting called. Is there any way i could read the reason for reboot. I want to read it so that i can get the reason that is stored. like 0xABADBABE is watchdog 0xCODEDEAD is panic. Etc.. Please suggest an alternative approach. Thanks, manty
On Tue, 02 Apr 2013 12:12:09 +0900, manty kuma said:
Is there any way i could read the reason for reboot. I want to read it so that i can get the reason that is stored. like 0xABADBABE is watchdog 0xCODEDEAD is panic. Etc..
Please suggest an alternative approach.
See the 'pstore' persistent storage filesystem in fs/pstore. That lets you store more than just an int (you can even get it to stash your dmesg buffer). 'more fs/pstore/Kconfig' would be a good place to start.
Hi Valdis, Thansk for answer. I have made use of saved_command_linbe buffer that is available in all modules(extern present in linux/init.h) Best Regards, Manty On Wed, Apr 3, 2013 at 3:07 AM, <Valdis.Kletnieks@vt.edu> wrote:
On Tue, 02 Apr 2013 12:12:09 +0900, manty kuma said:
Is there any way i could read the reason for reboot. I want to read it so that i can get the reason that is stored. like 0xABADBABE is watchdog 0xCODEDEAD is panic. Etc..
Please suggest an alternative approach.
See the 'pstore' persistent storage filesystem in fs/pstore. That lets you store more than just an int (you can even get it to stash your dmesg buffer).
'more fs/pstore/Kconfig' would be a good place to start.
participants (2)
-
manty kuma -
Valdis.Kletnieks＠vt.edu