Right now when a kernel oops/panic happens, a lot of text is dumped to the screen, most of which is not immediately understandable to the user encountering the problem. With the proposed approach, a QR code would be rendered that the user could then snap with a digital camera or smart-phone. From there the QR code could be decoded to expose the kernel error message in a more pleasant state than just being dumped to your screen. Approaches talked about would be either encoding the raw Linux kernel oops string or redirecting the user to a error message on Kernel.org. With the Kernel.org approach could potentially be also the automated reporting of the kernel oops. In order to make a long oops message fit within a reasonably sized QR code, gzip compression has been talked about for compressing the error string.
This is certainly an interesting approach to trying to better capture kernel oops messages. With my workflow, I would love to see this capability as well and would speed up some processes. Right now it looks like the developers working on these QR-packaged errors are currently getting the QR support into order.
the mailing list thread. Obviously this work is already out of the scope for the Linux 3.15 kernel but we look forward to its hopeful arrival in an upcoming kernel release.