OK, can you add to the command line:
to see if it's a specific function that may be causing the issue (but
hopefully it's not one of the scheduling functions that caused it).
Does it break if the crypto is not initialized? Perhaps add a command
line flag to have it happen earlier:
I didnt see any breakage, have been using ramoops with postcore_initcall
for sometime now.
and add a postcore_initcall that checks if that flag is set, and if so,
it does the work then, and the late_initcall() will do nothing.
That way, you can still have unmodified kernels use pstore when it
crashes at boot up.
Great, I guess you can write a patch to do that ;-)