Making bluescreens more useful

[Thomas Faber]

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.

Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...

Thoughts?

[David Quintana (gigaherz)]

Looks nice!

On 11 January 2018 at 00:48, Thomas Faber [e-mail] wrote:
> We often get bug reports with just a screenshot of a bluescreen; we then
> go ahead and tell people that bluescreens are basically useless, they
> should get a debug log and a backtrace, and also remember to tell us
> what version they're using.
>
> Since there's actually no reason why bluescreens need to be useless, I
> thought I'd try to change that.
> I've attached an example. The source for this quick PoC can be found at
> https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d472
> 99eec1971c
>
> Thoughts?
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Hermès BÉLUSCA-MAÏTO]

Let’s bring the NT-4-type BSODs back!! \o/

De : Ros-dev [mailto:[e-mail]] De la part de David Quintana (gigaherz)
Envoyé : jeudi 11 janvier 2018 00:53
À : ReactOS Development List
Objet : Re: [ros-dev] Making bluescreens more useful

Looks nice!

On 11 January 2018 at 00:48, Thomas Faber [e-mail] wrote:

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.

Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...

Thoughts?

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Pierre Schweitzer]

Good idea!
I would just have a few suggestions to make it even more useful:
- "Consider filing a ticket at https://jira.reactos.org/ if it wasn't
already reported there. To do so, provide information on what..."

- "Ideally, try to reproduce the problem while capturing a debug log
that you should translate afterwards.
See https://"

Cheers,
Pierre

Le 11/01/2018 à 00:48, Thomas Faber a écrit :
> We often get bug reports with just a screenshot of a bluescreen; we then
> go ahead and tell people that bluescreens are basically useless, they
> should get a debug log and a backtrace, and also remember to tell us
> what version they're using.
>
> Since there's actually no reason why bluescreens need to be useless, I
> thought I'd try to change that.
> I've attached an example. The source for this quick PoC can be found at
> https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
>
> Thoughts?
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.

[Colin Finck]

I'm supporting Thomas idea and Pierre's additional suggestions.
Let's show the world that BSODs can be useful!

- Colin

Am 11.01.2018 um 07:36 schrieb Pierre Schweitzer:
> Good idea!
> I would just have a few suggestions to make it even more useful:
> "Consider filing a ticket at https://jira.reactos.org/ if it wasn't
>
> already reported there. To do so, provide information on what..."
> "Ideally, try to reproduce the problem while capturing a debug log
>
> that you should translate afterwards.
> See https://"
>
> Cheers,
> Pierre
>
> Le 11/01/2018 à 00:48, Thomas Faber a écrit :
> > We often get bug reports with just a screenshot of a bluescreen; we then
> > go ahead and tell people that bluescreens are basically useless, they
> > should get a debug log and a backtrace, and also remember to tell us
> > what version they're using.
> >
> > Since there's actually no reason why bluescreens need to be useless, I
> > thought I'd try to change that.
> > I've attached an example. The source for this quick PoC can be found at
> > https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
> >
> > Thoughts?
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Michael Fritscher]

Hi,

yes, that would be very, very nice!

Michael

On 11.01.2018 11:45, Colin Finck wrote:
> I'm supporting Thomas idea and Pierre's additional suggestions.
> Let's show the world that BSODs can be useful!
> Colin
>
> Am 11.01.2018 um 07:36 schrieb Pierre Schweitzer:
> > Good idea!
> > I would just have a few suggestions to make it even more useful:
> > "Consider filing a ticket at https://jira.reactos.org/ if it wasn't
> >
> > already reported there. To do so, provide information on what..."
> > "Ideally, try to reproduce the problem while capturing a debug log
> >
> > that you should translate afterwards.
> > See https://"
> >
> > Cheers,
> > Pierre
> >
> > Le 11/01/2018 à 00:48, Thomas Faber a écrit :
> > > We often get bug reports with just a screenshot of a bluescreen; we then
> > > go ahead and tell people that bluescreens are basically useless, they
> > > should get a debug log and a backtrace, and also remember to tell us
> > > what version they're using.
> > >
> > > Since there's actually no reason why bluescreens need to be useless, I
> > > thought I'd try to change that.
> > > I've attached an example. The source for this quick PoC can be found at
> > > https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
> > >
> > > Thoughts?
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Timo Kreuzer]

I like it. I recently thought about another possibility to make the BSOD 
more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)

Am 11.01.2018 um 00:48 schrieb Thomas Faber:
> We often get bug reports with just a screenshot of a bluescreen; we then
> go ahead and tell people that bluescreens are basically useless, they
> should get a debug log and a backtrace, and also remember to tell us
> what version they're using.
>
> Since there's actually no reason why bluescreens need to be useless, I
> thought I'd try to change that.
> I've attached an example. The source for this quick PoC can be found at
> https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
>
> Thoughts?
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

Wouldn't the QR-enabled BSOD require us to draw the bsod screen in a
graphics mode rather than text?

Or are we using a graphics mode already?

On 12 January 2018 at 21:23, Timo Kreuzer [e-mail] wrote:
> I like it. I recently thought about another possibility to make the BSOD
> more useful: A QR code.
> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
>
> Here's a quick example (1425 characters)
> Try it out, use your phone and scan it :)
>
> Am 11.01.2018 um 00:48 schrieb Thomas Faber:
>
> We often get bug reports with just a screenshot of a bluescreen; we then
> go ahead and tell people that bluescreens are basically useless, they
> should get a debug log and a backtrace, and also remember to tell us
> what version they're using.
>
> Since there's actually no reason why bluescreens need to be useless, I
> thought I'd try to change that.
> I've attached an example. The source for this quick PoC can be found athttps://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
>
> Thoughts?
>
> Ros-dev mailing [e-mail]://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Hermès BÉLUSCA-MAÏTO]

Hi,

We use graphics already, via Inbv & bootvid calls. The same mode the ReactOS boot logo uses J

So this is definitively possible.

Of course we should also check whether the output is not done via headless instead, in which case of course there’s no need for the QR but instead one could just dump what the QR encodes directly on the terminal.

Hermès.

De : Ros-dev [mailto:[e-mail]] De la part de David Quintana (gigaherz)
Envoyé : vendredi 12 janvier 2018 22:00
À : ReactOS Development List
Objet : Re: [ros-dev] Making bluescreens more useful

Wouldn't the QR-enabled BSOD require us to draw the bsod screen in a graphics mode rather than text?

Or are we using a graphics mode already?

On 12 January 2018 at 21:23, Timo Kreuzer [e-mail] wrote:

I like it. I recently thought about another possibility to make the BSOD more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)

Am 11.01.2018 um 00:48 schrieb Thomas Faber:

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.

Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...

Thoughts?

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Hermès BÉLUSCA-MAÏTO]

Hi Timo !

Looks nice indeed :D But then we would need some “KeQrCodeGenerator” function (of some sorts, I let you think about the “NTOS” function prefix ^^) I suppose?

Best,

Hermès

De : Ros-dev [mailto:[e-mail]] De la part de Timo Kreuzer
Envoyé : vendredi 12 janvier 2018 21:23
À : [e-mail]
Objet : Re: [ros-dev] Making bluescreens more useful

I like it. I recently thought about another possibility to make the BSOD more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)

Am 11.01.2018 um 00:48 schrieb Thomas Faber:

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.

Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...

Thoughts?

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Alexander Shaposhnikov]

I like the idea! Mind the resolution though - the QR code must be readable.

12.01.2018 22:23, Timo Kreuzer пише:
> I like it. I recently thought about another possibility to make the
> BSOD more useful: A QR code.
> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
>
> Here's a quick example (1425 characters)
> Try it out, use your phone and scan it :)
>
> Am 11.01.2018 um 00:48 schrieb Thomas Faber:
> > We often get bug reports with just a screenshot of a bluescreen; we then
> > go ahead and tell people that bluescreens are basically useless, they
> > should get a debug log and a backtrace, and also remember to tell us
> > what version they're using.
> >
> > Since there's actually no reason why bluescreens need to be useless, I
> > thought I'd try to change that.
> > I've attached an example. The source for this quick PoC can be found at
> > https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
> >
> > Thoughts?
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
Cheers,
Alexander Shaposhnikov

[Ged Murphy]

You’ve been looking at too many Win10 blue screens 😉

From: Ros-dev [mailto:[e-mail]] On Behalf Of Timo Kreuzer
Sent: 12 January 2018 20:23
To: [e-mail]
Subject: Re: [ros-dev] Making bluescreens more useful

I like it. I recently thought about another possibility to make the BSOD more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)

Am 11.01.2018 um 00:48 schrieb Thomas Faber:

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.

Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...

Thoughts?

_______________________________________________
Ros-dev mailing list
[e-mail] mailto:[e-mail] 
http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

Whatever we do, DO NOT put a smiley in it. It feels like an insult.

On 13 January 2018 at 10:36, Ged Murphy [e-mail]
wrote:
> You’ve been looking at too many Win10 blue screens 😉
>
> *From:* Ros-dev [mailto:[e-mail]] *On Behalf Of *Timo
> Kreuzer
> *Sent:* 12 January 2018 20:23
> *To:* [e-mail]
> *Subject:* Re: [ros-dev] Making bluescreens more useful
>
> I like it. I recently thought about another possibility to make the BSOD
> more useful: A QR code.
> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
>
> Here's a quick example (1425 characters)
> Try it out, use your phone and scan it :)
>
> Am 11.01.2018 um 00:48 schrieb Thomas Faber:
>
> We often get bug reports with just a screenshot of a bluescreen; we then
>
> go ahead and tell people that bluescreens are basically useless, they
>
> should get a debug log and a backtrace, and also remember to tell us
>
> what version they're using.
>
> Since there's actually no reason why bluescreens need to be useless, I
>
> thought I'd try to change that.
>
> I've attached an example. The source for this quick PoC can be found at
>
> https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299ee...
>
> Thoughts?
>
> Ros-dev mailing list
>
> [e-mail]
>
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Amine Khaldi]

> I like it. I recently thought about another possibility to make the 
> BSOD more useful: A QR code.
> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

As our friends at Haiku have already implemented something like this 
ages ago, it would be nice to finally have this in ReactOS too :)

https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/

[Javier Agustìn Fernàndez Arroyo]

i like the QR thing. But, take in mind that we will need some kind of
decoder into JIRA, website, or wherever, so that they are easily
uploadable/reportable....

On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldi [e-mail]
wrote:
> I like it. I recently thought about another possibility to make the BSOD
> > more useful: A QR code.
> > A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
>
> As our friends at Haiku have already implemented something like this ages
> ago, it would be nice to finally have this in ReactOS too :)
>
> https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

Yep, there's plenty of QR readers that we can use, that's really not a
problem at all.

On 14 January 2018 at 12:32, Alexander Rechitskiy [e-mail]
wrote:
> https://github.com/libern/qr-code-reader
>
> https://github.com/schmich/instascan
>
> 14.01.2018, 14:24, "Javier Agustìn Fernàndez Arroyo" [e-mail]:
>
> i like the QR thing. But, take in mind that we will need some kind of
> decoder into JIRA, website, or wherever, so that they are easily
> uploadable/reportable....
>
> On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldi [e-mail]
> wrote:
>
> I like it. I recently thought about another possibility to make the BSOD
> more useful: A QR code.
> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
> As our friends at Haiku have already implemented something like this ages
> ago, it would be nice to finally have this in ReactOS too :)
>
> https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ,
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
> Best regards,
> Alexander Rechitskiy
> [phone]
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev