Intel Linux Display Driver Being Adapted For DRM Panic "Blue Screen of Death" Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • oiaohm
    replied
    Originally posted by turtleidiot View Post
    That's all. You still have other methods of getting the kernel logs if you absolutely need them, like serial.
    Depends on what is crashing there have been historic issues with serial interfaces.

    Big thing is the QR code from the Linux kernel unless you screen is huge it contains more data than you can display on screen at text.

    There are pro and cons to the QR code. Yes the generator of the QR code could be having issues this is why it has a off switch.

    Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.


    turtleidiot the documentation on a lot of Linux kernel command line options is in the last place most users would ever look. Yes hidden in one of the Kconfig files of the Linux kernel.

    Yes you can see the QR code depends on select ZLIB_DEFLATE because the message contents in the QR code is in fact compressed. Getting the last lines of the kmesg as what is the no QR code option results in lots of cases less information on what in fact went wrong.

    I understanding not likely QR code. Machine readable has a data density advantage over text.

    Leave a comment:


  • turtleidiot
    replied
    Originally posted by intelfx View Post

    Obviously, it does exist. It's called drm.panic_screen=. This is just typical Moronix outrage.
    Thank you, I searched a bunch of places and couldn't find anything about a boot parameter. Glad to know it's there

    Leave a comment:


  • intelfx
    replied
    Originally posted by turtleidiot View Post

    The QR code feature can be enabled/disabled at build time with a build switch. I agree it would be nice to have a boot parameter for this as well if it doesn't exist
    Obviously, it does exist. It's called drm.panic_screen=. That was just typical Moronix outrage.
    Last edited by intelfx; 05 December 2024, 11:22 AM.

    Leave a comment:


  • User29
    replied
    Originally posted by turtleidiot View Post
    As for your second point, I don't really see how the QR panic message is comparable to QR code menus.
    they'll know you are using linux. and they​ will turn this knowledge against you.

    Leave a comment:


  • turtleidiot
    replied
    Originally posted by Danny3 View Post
    Well I hope that this Qr crap is optional as I hate to depend on a phone to be able to read error messages.
    It's enough that so many asshole restaurants and pizzerias don't give you a menu anymore and force you to use your phone to visit a tracking infested website to view the menu!
    Fuck this shitty trend!
    The QR code feature can be enabled/disabled at build time with a build switch. I agree it would be nice to have a boot parameter for this as well if it doesn't exist but I can imagine there may be some architectural reasons why it can't.
    As for your second point, I don't really see how the QR panic message is comparable to QR code menus.
    QR code menus are made to track people, serve them ads, etc. and don't even work that well. And I completely agree with you, they suck!
    The kernel panic feature is made to simply get the kernel logs in your notes/an email/a message as fast as possible without manually transcribing them. That's all. You still have other methods of getting the kernel logs if you absolutely need them, like serial.

    Leave a comment:


  • Danny3
    replied
    Well I hope that this Qr crap is optional as I hate to depend on a phone to be able to read error messages.
    It's enough that so many asshole restaurants and pizzerias don't give you a menu anymore and force you to use your phone to visit a tracking infested website to view the menu!
    Fuck this shitty trend!

    Leave a comment:


  • turtleidiot
    replied
    Great to see the QR code panic messages gaining traction.
    Or at least it's great to see useful QR code panic messages (cough Windows cough)

    Leave a comment:


  • dragon321
    replied
    Inb4 comments like "OS should never crash" or "Linux is becoming Windows"

    It appears that NVIDIA's proprietary driver may also support it, as one of their employees confirmed that they are tracking it internally.
    Last edited by dragon321; 04 December 2024, 07:13 PM.

    Leave a comment:


  • Intel Linux Display Driver Being Adapted For DRM Panic "Blue Screen of Death" Support

    Phoronix: Intel Linux Display Driver Being Adapted For DRM Panic "Blue Screen of Death" Support

    The DRM Panic infrastructure has been in the Linux kernel for several releases now and allows for a kernel-based experience similar to Windows' "Blue Screen of Death as well as more recently allowing QR code kernel error messages and other features. The Intel kernel DRM driver has seen some patches for enabling DRM Panic support...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Working...
X