Stefan,
Am Montag, 21. Mai 2018, 04:29:24 CEST schrieb Stefan Schaeckeler:
> Hello Richard and others,
>
> > I get the use-case, but why is this only for mtdoops?
>
> Powerpc's nvram module also stores oops messages and does so by adding an
> additional timestamp, as well (search for kmsg_dump_g
Hello Richard and others,
> I get the use-case, but why is this only for mtdoops?
Powerpc's nvram module also stores oops messages and does so by adding an
additional timestamp, as well (search for kmsg_dump_get_buffer() in
arch/powerpc/kernel/nvram_64.c).
This timestamp is the number of seconds
Hi Stefan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mtd/master]
[also build test WARNING on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/l
Stefan,
Am Sonntag, 20. Mai 2018, 05:39:40 CEST schrieb Stefan M Schaeckeler:
> Optionally dump boottime on the mtd device in the form of
>
> <0>[ 0.00] Boot time mm/dd/ hh:mm:ss
>
> Time-stamps of oops messages are in seconds since boottime. Recording also
> the boottime helps correla
Optionally dump boottime on the mtd device in the form of
<0>[ 0.00] Boot time mm/dd/ hh:mm:ss
Time-stamps of oops messages are in seconds since boottime. Recording also
the boottime helps correlating oopses with other events having occured at
the same time. This correlation will be oth
5 matches
Mail list logo
