Linked by Thom Holwerda on Mon 2nd Jul 2012 18:19 UTC, submitted by anonymous
BeOS & Derivatives Michael Lotz added code to generate QR-code for the KDL (Kernel Debug Land) ouput (which pops up when the kernel crashes). No more blurry photos with debug output, but a QR code which decodes to the clear-text KDL debug output. Here's one of the relevant commits, an example showing a QR code, and text from decoded sample QR code.
Thread beginning with comment 524947
To view parent comment, click here.
To read all comments associated with this story, please click here.
by phoudoin on Tue 3rd Jul 2012 09:24 UTC in reply to "RE[2]: WTF IS THIS SHIT"
Member since:

While running Windows, remove your system SATA disk/ssd and check how it works fine.
Now imagine that instead of human removal the cause is disk controler going crazy sometimes, not definitively. Or it's manufacturer driver is immature and don't have this quicky hardware workaround (disclaimer: all kernel crashes appearing in this comment are fictitious. Any resemblance to real ones, pending or past, is purely coincidental...)

How do you get enough data to discover the root cause?

Plus, please notice that Haiku don't have the resources Microsoft had to wrote its Windows kernel, and still it took a lot of time to reach a mature kernel crash features set. And calling the bluescreen a mature kernel debugger is kinda funny, BTW...

Edited 2012-07-03 09:39 UTC

Reply Parent Score: 3