Skip to contentSkip to conversation

oops pauser.

DISCUSSION Robert Hancock 6 participants 7 messages Jan 6, 2006 – Jan 15, 2006 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 2 lines · Dave Jones

After an oops, we can't really rely on anything. What if the oops came from the console layer, or a framebuffer driver?

In this case, maybe it wouldn't work.. but I think it would be helpful a big majority of the time.

Surely there must be a way this could be done. After all, Windows seems to manage to fairly reliably switch the display into VGA 80x50 mode and put up the BSOD with error dump information with reasonably good reliability..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#4 lore raw
Quoted 2 lines
Quoted 2 lines

After an oops, we can't really rely on anything. What if the oops came from the console layer, or a framebuffer driver?

How about this?:

Put an "emergency kernel" into a memory location that is being protected in some way (i.e. writing there even from kernel space generates an oops). Upon oops, it gets unlocked and we do some sort of kexec() to it. Of course, this probably requires that the unlocking must not be done with help of the standard page mappings.

Jan Engelhardt

#5 lore raw
Quoted 10 lines · On Fri, 6 Jan 2006 08:06:12 +0100 (MET) Jan Engelhardt wrote:
Quoted 2 lines
Quoted 2 lines

After an oops, we can't really rely on anything. What if the oops came from the console layer, or a framebuffer driver?

How about this?:

Put an "emergency kernel" into a memory location that is being protected in some way (i.e. writing there even from kernel space generates an oops). Upon oops, it gets unlocked and we do some sort of kexec() to it. Of course, this probably requires that the unlocking must not be done with help of the standard page mappings.

This is what kexec + kdump is.

---
~Randy

#6 lore raw
In reply to Jan Engelhardt
Quoted 8 lines · Jan Engelhardt
Quoted 2 lines
Quoted 2 lines

After an oops, we can't really rely on anything. What if the oops came from the console layer, or a framebuffer driver?

How about this?:

Put an "emergency kernel" into a memory location that is being protected in some way (i.e. writing there even from kernel space generates an oops). Upon oops, it gets unlocked and we do some sort of kexec() to it.

You just reinvented 'kdump' :)
There's been ongoing work in this area for a while.

Dave

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw

Re: Console debugging wishlist was: Re: oops pauser.

Quoted 2 lines · Andi Kleen

(it is hard to understand that with 128MB+ graphic cards and 512+MB computers the scroll back must be still so short...)

The VGA scrollback buffer is limited by the text area of the video RAM. The text area is in the DOS memory at 0xB800 (or 0xB000) and extends 32 KB (or in case of MDA, 4 KB). Each character will use 2 Bytes. Therefore you can store up to 16,000 characters or 4 pages of text.

Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
#9 lore raw

Re: Console debugging wishlist was: Re: oops pauser.

Quoted 9 lines · Bodo Eggert
Quoted 2 lines · Andi Kleen

(it is hard to understand that with 128MB+ graphic cards and 512+MB computers the scroll back must be still so short...)

The VGA scrollback buffer is limited by the text area of the video RAM. The text area is in the DOS memory at 0xB800 (or 0xB000) and extends 32 KB (or in case of MDA, 4 KB). Each character will use 2 Bytes. Therefore you can store up to 16,000 characters or 4 pages of text.

It was a rhetorical question.

-Andi

#10 lore raw

Re: Console debugging wishlist was: Re: oops pauser.

Quoted 10 lines
Quoted 7 lines
Quoted 2 lines

(it is hard to understand that with 128MB+ graphic cards and 512+MB computers the scroll back must be still so short...)

The VGA scrollback buffer is limited by the text area of the video RAM. The text area is in the DOS memory at 0xB800 (or 0xB000) and extends 32 KB (or in case of MDA, 4 KB). Each character will use 2 Bytes. Therefore you can store up to 16,000 characters or 4 pages of text.

It was a rhetorical question.

And I assumed that scrollback was stored in some regular kmalloc()ed page(s).

Jan Engelhardt