Re: [Ksummit-discuss] Fwd: [TECH TOPIC] QR encoded oops for the kernel

[Daniel Vetter <daniel.vetter@ffwll.ch>]

On Wed, May 14, 2014 at 10:00 PM, Levente Kurusa <levex@linux.com> wrote:
> On Wed, May 14, 2014 at 11:54:49AM -0700, Josh Triplett wrote:
>> On Wed, May 14, 2014 at 09:00:51AM -0700, H. Peter Anvin wrote:
>> > On 05/13/2014 12:08 AM, Josh Triplett wrote:
>> > >
>> > > Many users will already have a QR-code scanning app installed, and such
>> > > apps always support loading URLs in a browser.
>> > >
>> >
>> > Let me disavow you of the notion that stock scanning apps handle large
>> > QR symbols.
>>
>> That's certainly true.  On the other hand, I'd really like to see a
>> version of the oops-as-QR-code bits that uses VGA block characters to
>> work in non-graphics, non-framebuffer mode, which would require fitting
>> in at most 80x50 (using the half-block characters).  That wouldn't allow
>> nearly as much data, but likely enough for a somewhat useful crash
>> report, especially in aggregate.
>
> Not really possible, from my experiences the QR code that results from
> a random oops is ranging from 100x100 to 150x150 depending on the size
> of stack trace and stuff like that. Of course, we can decrease the
> error recovery region and that might make it smaller. I'll take a look
> at this a bit later. If that doesn't work, then that means that we can't
> shuffle that into the textmode's 80x25. Not to mention that the block
> characters in the ASCII table (I think you meant that, if not please
> correct me) are not neccessarily square, which is needed for maximum
> scannability.
>
> One thing that we currently support and can be a solution is Micro QR
> code. It removes two of the three coordinators and does some more
> compression AFAIK. It might be possible to shuffle that into textmode.
>
> I as well would love to support QR codes in textmode, but I think that
> it's really not possible at the moment.

David Herrman is working on some new infrastructure for emergency log
services on top of drm/kms drivers since we really, really want to
move away from the horrors called fbcon. His design is fairly neat and
there shouldn't be that big an issue with replacing the current
character-painting code he has with some oops-painting code. Adding
him to the discussion so he can point at some of the patches.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch