How to store kernel panic/oops
Quoted 2 lines · David Woodhouse
Can't it be done with what's in the tree already? Just create an MTD device using phram or something else, then point mtdoops at it
Yes of course, if possible we shouldn't reinvent the wheel but I wondered if there was something more specific. To add mtdoops (more or less 1k) we have to add mtd subsys (more or less 14k) to the kernel to achieve this and it's all overhead.
Marco
Quoted 10 lines · Marco Stornelli
Quoted 2 lines · David Woodhouse
Can't it be done with what's in the tree already? Just create an MTD device using phram or something else, then point mtdoops at it
Yes of course, if possible we shouldn't reinvent the wheel but I wondered if there was something more specific. To add mtdoops (more or less 1k) we have to add mtd subsys (more or less 14k) to the kernel to achieve this and it's all overhead.
panic/oops information is punted down to a kmsg dumper, which mtdoops just happens to be one of. If you wanted to do your own platform specific hack for size constraints you could easily just have your own special one instead. Take a look at linux/kmsg_dump.h.