Red Hat Engineer Working On DRM Panic Support For AMDGPU Driver

[intelfx]

Nah, it just means that now the developers have to tell people to disable the dumb error screen and give them a damn stacktrace. Your mindeset is wasting their time.

You do realize, right, that the entire point of the "dumb error screen" is precisely to convey the stacktrace in a form that's guaranteed to be machine-readable and not truncated (unlike the wah wah my non-dumb text diarrhea that the user will have to photograph and even then it will be truncated in 90% of cases, making it useless to a developer)?

Your mindset is wasting the developers' time. Congrats, you just played yourself.

[varikonniemi]

You do realize, right, that the entire point of the "dumb error screen" is precisely to convey the stacktrace in a form that's guaranteed to be machine-readable and not truncated (unlike the wah wah my non-dumb text diarrhea that the user will have to photograph and even then it will be truncated in 90% of cases, making it useless to a developer)?

Your mindset is wasting the developers' time. Congrats, you just played yourself.

Indeed. If i understand correctly, currently a panic while in DRM driver results in screen freezing. Only if panic happens while in VT do you get the text output. So this DRM panic QR code work also brings the possibility of getting the typical text on screen even if on the desktop, so it's an improvement across the board.

And indeed it's better to code the text into a QR code, because then you can copy&paste it to the bug report without having to type it out. In today's age we can expect that the user is able to get access to some form of camera to save the QR code, even if not a mobile phone with QR scanner.

[QwertyChouskie]

I haven't seen any kernel panics in years. What am I doing wrong? I feel like I'm missing out on something.

My understanding is that displaying kernel panics has been broken for years, which was the core motivator for the DRM Panic work. Things like QR codes encoding the error log are a nice bonus, but the real improvement is seeing the error at all rather than just a frozen screen.

[skeevy420]

Indeed. If i understand correctly, currently a panic while in DRM driver results in screen freezing. Only if panic happens while in VT do you get the text output. So this DRM panic QR code work also brings the possibility of getting the typical text on screen even if on the desktop, so it's an improvement across the board.

And indeed it's better to code the text into a QR code, because then you can copy&paste it to the bug report without having to type it out. In today's age we can expect that the user is able to get access to some form of camera to save the QR code, even if not a mobile phone with QR scanner.

People seem to be so oblivious to how helpful QR codes actually are.

Before shit would freeze leaving us with maybe have access to a screen with an error message and then that error may or may not be available after boot. If you were in a graphical session, you were likely up Shit Creek if you wanted an error message. So if you were one of the few set up in a way where you actually got the error message your only options were to write it down by hand, take a picture, or, like graphical users, hope your system had some sort of log dumping strategy going on.

If you took the picture or wrote it down you'd have to use some form of OCR to convert that to some sort of workable text for a developer to use which is a pain in the ass process that the average person isn't going to do. The average person is likely going to be one of those assholes that posts 800 lines of text in a photo in the wrong aspect ratio. With a QR code we can give the developer an exact copy/paste of the error and with QR error correction and perspective correction the developers don't have to worry that some of us can't frame a photo.

We have this open standard, royalty free method that can graphically convey large enough amounts of information to make low-level logging and error reporting accessible to the masses and we can do so in a way that works for graphical and text-based environments ... Nah, forget that idea. It's upsetting a few Devuan users.

[Espionage724]

And some people are like "I love this QR and systemd stuff... I love Windows and should really be using that instead of anything else".

In-case anyone else wasn't aware, there's Windows 11 24H2 LTSC

[Kemosabe]

I guess seeing a QR code is nicer than seeing glitched graphics everywhere after resuming from suspend...

Because if the graphics are glitched, a QR code is not. . . wait a minute.

[varikonniemi]

Because if the graphics are glitched, a QR code is not. . . wait a minute.

Indeed, after this you will instead of seeing glitched screen/black screen/frozen screen a nice QR code or DMESG output.

[Developer12]

This is going to be an embarrassment on the face of the linux user experience for decades to come. I want to know why the fuck my computer just crashed and where my work just went, not stare at a piece of abstract art.

[oiaohm]

This is going to be an embarrassment on the face of the linux user experience for decades to come. I want to know why the fuck my computer just crashed and where my work just went, not stare at a piece of abstract art.

Not really compare to the historic I had when I was running Nvidia of kernel panic while using X11 with a stack of strange color dots across the top of screen to decode to get the dmesg this is a improvement.

Lot of ways this is also better than the historic problem of is system just doing a ice station or crashed. Yes something you can still do building too many thing at once and have the interface of Linux completely lag out but will recover this is icestation or has it crashed. Yes the few dots different along the top of screen being the only difference was absolute not great to wake up you have left a system for hour plus because you though it was doing a icestation and still processing but the thing was crashed the complete time.

DRM Panic support is that you do get a output. QR code on screen where there should not be will be clear the system is dead.

Some ways if we were being arty have the TUX logo with the QR code in belly for crash message with line under it looks like I ate something bad here.

[Developer12]

Not really compare to the historic I had when I was running Nvidia of kernel panic while using X11 with a stack of strange color dots across the top of screen to decode to get the dmesg this is a improvement.

Lot of ways this is also better than the historic problem of is system just doing a ice station or crashed. Yes something you can still do building too many thing at once and have the interface of Linux completely lag out but will recover this is icestation or has it crashed. Yes the few dots different along the top of screen being the only difference was absolute not great to wake up you have left a system for hour plus because you though it was doing a icestation and still processing but the thing was crashed the complete time.

DRM Panic support is that you do get a output. QR code on screen where there should not be will be clear the system is dead.

Some ways if we were being arty have the TUX logo with the QR code in belly for crash message with line under it looks like I ate something bad here.

How about text!? Even the windows bluescreen which they're ripping this off from has plain messages telling you what kind of error is it and what driver it came from.

Leave it to linux to rip off a user interface and leave out stuff critical to the user experience. It's part of why accessibility is such absolute crap.