Skip to contentSkip to conversation

Panicking in morse code

PATCH Andi Kleen 4 participants 5 messages Jul 19, 2002 – Jul 21, 2002 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): 20020719011300.548d72d5.arodland@noln.com.suse.lists.linux.kernel

Andi Kleen

author
#1 lore raw
Quoted 4 lines · Andrew Rodland

I was researching panic_blink() for someone who needed a little help, when I noticed the comment above the function definition, not being the kind to step down from a challenge (unless it's just really hard), I decided to write morse code output code.

Great. Congratulations (having written the original comment).

I would encode the morse strings as bits in a integer instead of strings though (perhaps with some macros to make it readable), that should shrink it quite a bit.

Quoted 10 lines

The option panicblink= has been hijacked to be a simple bitfield:
bit 1 : blink LEDs
bit 2 : sound the PC speaker.

the blinking option depends only on pc_keyb.c. the pcspeaker option depends on kb_mksound() actually doing something. At the moment, both of these mean i386. The call to panic_blink() in panic() is still guarded by an i386 #ifdef, anyway, for the moment. The default is to blink only, because I figured the beeps would be too annoying. Opinions?

I would consider beeps annoying, but then I usually just cut the beeper line on any new PC I install so personally I do not care. Still imagine what a machine room that overheated and caused several boxes to panic would sound like...

-Andi

#2 lore raw
Quoted 11 lines · you [Andi Kleen]
Quoted 4 lines · Andrew Rodland

I was researching panic_blink() for someone who needed a little help, when I noticed the comment above the function definition, not being the kind to step down from a challenge (unless it's just really hard), I decided to write morse code output code.

I would consider beeps annoying, but then I usually just cut the beeper line on any new PC I install so personally I do not care. Still imagine what a machine room that overheated and caused several boxes to panic would sound like...

I'm just waiting for Andrew to come up with a proper morse code network layer, so that the machines in the room can communicate (provided they have a mic each)... Now combine that with Ingo's network console and...

-- v --

[email protected]

#3 lore raw

On Sat, 20 Jul 2002, Ville Herva wrote:
[...]

Quoted 3 lines

I'm just waiting for Andrew to come up with a proper morse code network layer, so that the machines in the room can communicate (provided they have a mic each)... Now combine that with Ingo's network console and...

You mean like an implementation of RFC 1926: "An Experimental Encapsulation of IP Datagrams on Top of ATM[1]"? ;-)

Neale.

[1] ATM: in this case it's "Acoustical Transmission Media"

#4 lore raw

Hi,

Quoted 2 lines · Neale Banks

You mean like an implementation of RFC 1926: "An Experimental Encapsulation of IP Datagrams on Top of ATM[1]"? ;-)

The author assumes that the users take whatever precautions that are necessary before attempting to use this protocol in any crowded area.

Same thing to add here...

Regards, Thunder

Signature · 7 lines
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o?  K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y- 
------END GEEK CODE BLOCK------

A message that is not in the archive (sent off-list or not yet received): 20020720173222.3286fcbb.arodland@noln.com.suse.lists.linux.kernel

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): 20020721100818.A22176@flint.arm.linux.org.uk.suse.lists.linux.kernel

author
#8 lore raw

Re: [PATCH -ac] Panicking in morse code v3

Quoted 5 lines · Russell King

Hmm. I thought the original idea for the "flash LEDs on panic" was so you knew something had gone wrong early in the boot, at the kind of places where you don't have a console initialised. If you don't have the console initialised, you sure as hell don't have the input layer or keyboard drivers initialised.

[having written the original code...]
The idea was to distingush panic from lockup when you are in X and cannot see the console and X is dead so you cannot switch to the console.

Handling early panic is probably better done by an "early console", like x86-64 supports one.

-Andi