On Sat 13 Jun 2009 14:59, Wolfgang Denk pondered: > Dear Russell King, > > In message <20090613102642.gb7...@flint.arm.linux.org.uk> you wrote: > > > > The other way I've seen people read out crash messages is using a > > debugger to dump the kernel's log buffer directly. That seems to work > > as well as any other method, and has the advantage that it doesn't > > require any kernel modifications. > > This works well in the lab during hardware bringup or BSP development. > > But we are also interested in a solution that allows to get more or > less automatic access to the log buffer content after a crash - when > you have several ten thousand systems in the field, such a feature > can save you a lot of money.
in this case - is it true that providing the kernel crash log buffer to the next running kernel - is actually more important than just giving it to the bootloader? (Since the bootloader may not have the facilities to email/post/netcat it to a developer - like the next running kernel might?) In this case - the Bootloader being able to read the buffer, understand that there was a crash, and be able to pass the buffer (with the crash message) into the next running kernel - where that kernel can package it up and do anything it wants to it - would be a requirement? -Robin -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
