> There lies the issue: if I set panic_print to dump all backtraces, task > info and memory state in a panic event, that information + the > panic/oops and some previous relevant stuff, does it all fit in the 2M > chunk? Likely so, but *if it doesn't fit*, we may lose _exactly_ the > most important piece, which is the panic cause. That does change things ... I wonder how many megabytes you need for a big system (hundreds of cores, thousands of tasks)! This use case does look like it could use multiple chunks in ramoops. -Tony