Skip to contentSkip to conversation

2.5.59 morse code panics

PATCH Andi Kleen 13 participants 19 messages Jan 31, 2003 – Feb 7, 2003 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): 20030131104326.GF12286@louise.pinerecords.com.suse.lists.linux.kernel

A message that is not in the archive (sent off-list or not yet received): 200301311112.h0VBCv00000575@darkstar.example.net.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): 1044025785.1654.13.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel

Andi Kleen

author
#4 lore raw
Quoted 8 lines · Alan Cox
Quoted 3 lines · Dave Jones

Or you could put down the crackpipe and run a serial console between the two boxes. Or even netconsole would make more sense (and be a lot more reliable).

A lot of newer laptops do not have serial ports. While morse code may be a little silly the general purpose hook it needs to be done cleanly is considerably more useful

And how many users and how many kernel hackers are able to decode morse on the fly? Are you going to explain to users
"to debug this you'll need to learn morse" ?

If you want to make debugging easy for laptops write a USB or firewire console. Firewire is actually quite interesting because it can even do DMA, so you could peek into the memory.

Morse is not helpful.

I admit I was the on who got this ball running by suggesting it "as an exercise for the reader" in the original panic blink code, but guys this was intended as a JOKE, not serious. Please get over it and don't merge that silly code.

Thanks,
-Andi

#5 lore raw
Quoted 3 lines

[[email protected]]

Morse is not helpful.

Of course it is, you're just angry that I've left out your original plain_blinking code.

*runs*

#6 lore raw
Quoted 3 lines
Quoted 1 line

Morse is not helpful.

Of course it is

Especially since a number of Linux developers have ham radio experience.

Quoted 2 lines

you're just angry that I've left out your original plain_blinking code.

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

John.

#7 lore raw
Quoted 4 lines

[[email protected]]

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Because that's going to make reading the morse much harder.

Signature · 1 line
Tomas Szepe <[email protected]>
#8 lore raw
Quoted 4 lines
Quoted 2 lines

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Because that's going to make reading the morse much harder.

Err, I was joking, that was not a serious suggestion :-)

John.

#9 lore raw
In reply to John Bradford

John Bradford <[email protected]> said:

[...]

Quoted 5 lines
Quoted 2 lines

you're just angry that I've left out your original plain_blinking code.

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Then put out the stuff in octal...

/me dives for a hiding place

Signature · 4 lines
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
#10 lore raw
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

you're just angry that I've left out your original plain_blinking code.

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Then put out the stuff in octal...

Or maybe even have a nice scrolling binary display...

John.

#11 lore raw
Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

you're just angry that I've left out your original plain_blinking code.

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Then put out the stuff in octal...

Or maybe even have a nice scrolling binary display...

Or even better, time it so that when you twirl the keyboard around by its cord in a dark room, the LEDs print the message into the air a-la the skyliner
(http://www.theskyliner.com/)

/me ducks

-Eric

Signature · 5 lines
------------------------------------------------------------
        Eric H. Weigle -- http://public.lanl.gov/ehw/
"They that can give up essential liberty to obtain a little
temporary safety deserve neither" -- Benjamin Franklin
------------------------------------------------------------
#12 lore raw
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

you're just angry that I've left out your original plain_blinking code.

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Quoted 7 lines
Quoted 2 lines
Quoted 1 line

Then put out the stuff in octal...

Or maybe even have a nice scrolling binary display...

Or even better, time it so that when you twirl the keyboard around by its cord in a dark room, the LEDs print the message into the air a-la the skyliner

(http://www.theskyliner.com/)

Might be a problem for cordless keyboards, though - not sure how we'd support those.

John.

#13 lore raw
In reply to John Bradford
Quoted 2 lines · John Bradford

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Sure, alternating on/off between the outside LEDs at a rate of about 1/sec, like the warning lights on a railroad crossing (in the USA).

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#14 lore raw
Quoted 6 lines · Bill Davidsen
Quoted 2 lines · John Bradford

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Sure, alternating on/off between the outside LEDs at a rate of about 1/sec, like the warning lights on a railroad crossing (in the USA).

<nonsense>
As long as this doesn't mean a 50.000 kilo locomotive will ride over my keyboard, it is fine with me.

Oh, and I don't want to destroy the American dream, but blinking lights on railroad crossings even exist in the poorest countries in Africa... Or do the Americans even have a patent on the blinking speed ? :-P

Sidenote: you can't speak of "the middle", the LED ordering is free :) At least here in Europe...
</nonsense>

Besides, I'd like to see some beeps (not too annoying please) besides the blinking. Sometimes while debugging KGI I don't even notice the kernel entered kdb (also blinking LEDs, and kdb shows up on a remote terminal).
Also: servers will usually have keyboard switches, making the blinks unnoted. But I assume that has been said before.

Jos

#15 lore raw
Quoted 8 lines · Jos Hulzink
Quoted 6 lines · Bill Davidsen
Quoted 2 lines · John Bradford

Well, there are typically *three* keyboard LEDs... Why not use one the middle one for morse, and outside two for plain blinking?

Sure, alternating on/off between the outside LEDs at a rate of about 1/sec, like the warning lights on a railroad crossing (in the USA).

Quoted 7 lines

<nonsense>
As long as this doesn't mean a 50.000 kilo locomotive will ride over my keyboard, it is fine with me.

Oh, and I don't want to destroy the American dream, but blinking lights on railroad crossings even exist in the poorest countries in Africa... Or do the Americans even have a patent on the blinking speed ? :-P

In the USA thry are two, horizontal, in England I saw some up near Thursk which were vertical. Avoiding US-centerism I clarified where I saw them, rather than assuming that they would be the same everywhere...

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#16 lore raw
In reply to John Bradford
Quoted 2 lines · John Bradford

Especially since a number of Linux developers have ham radio experience.

Well most linux users don't. I'm sure its really easy to find a morse code chart in many hundreds of places online. But 2 scripts - one that turns keyboard input or mic input into dots and dashes (so you can enter it yourself or put the phone up to the system's microphone) would help. Then all you'd need is a morse->ascii converter.

So who's got a good morse->ascii program? And who has the dot-dash->.-.-.- translator? And the audio->.-.-.- translator?

-Peter

Signature · 6 lines
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.

Plan 2: If you're going to apologize, don't do it.  If you're going to 
do it, don't apologize
#17 lore raw
Quoted 4 lines · Peter C. Norton
Quoted 2 lines · John Bradford

Especially since a number of Linux developers have ham radio experience.

Quoted 8 lines

Well most linux users don't. I'm sure its really easy to find a morse code chart in many hundreds of places online. But 2 scripts - one that turns keyboard input or mic input into dots and dashes (so you can enter it yourself or put the phone up to the system's microphone) would help. Then all you'd need is a morse->ascii converter.

So who's got a good morse->ascii program? And who has the dot-dash->.-.-.- translator? And the audio->.-.-.- translator?

emacs (I'm not a user, though) has something like M-x-morse that will convert back and forth.

Otherwise, the basic tables are fairly easy to find - I've seen multiple filters for various IRC clients that would convert in at least one direction.

In any case, there are two things to remember here:
1) This may occassionaly be helpful in debugging problems.
2) It has a nice hack value to it.

Quoted 16 lines

-Peter

Signature · 12 lines
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.

Plan 2: If you're going to apologize, don't do it.  If you're going to 
do it, don't apologize

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Signature · 2 lines
Ryan Anderson
  sometimes Pug Majere
#18 lore raw
Quoted 11 lines
Quoted 11 lines
Quoted 2 lines

Especially since a number of Linux developers have ham radio experience.

Well most linux users don't. I'm sure its really easy to find a morse code chart in many hundreds of places online. But 2 scripts - one that turns keyboard input or mic input into dots and dashes (so you can enter it yourself or put the phone up to the system's microphone) would help. Then all you'd need is a morse->ascii converter.

So who's got a good morse->ascii program? And who has the dot-dash->.-.-.- translator? And the audio->.-.-.- translator?

We already discussed the idea of a userspace program to decode the morse:

http://marc.theaimsgroup.com/?l=linux-kernel&m=104401177724846&w=2

Quoted 2 lines

emacs (I'm not a user, though) has something like M-x-morse that will convert back and forth.

Yes, M-x morse-region.

John.

#19 lore raw
In reply to Andi Kleen
Quoted 2 lines · Andi Kleen

If you want to make debugging easy for laptops write a USB or firewire console.

irda too maybe ?

Quoted 2 lines

Firewire is actually quite interesting because it can even do DMA, so you could peek into the memory.

kgdb-over-firewire ? 8-)

Quoted 6 lines

Morse is not helpful.

I admit I was the on who got this ball running by suggesting it "as an exercise for the reader" in the original panic blink code, but guys this was intended as a JOKE, not serious. Please get over it and don't merge that silly code.

A voice of sanity.. I think you made a monster with that comment 8-)

Dave

Signature · 2 lines
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs
#20 lore raw
Quoted 6 lines · Dave Jones
Quoted 2 lines · Andi Kleen

If you want to make debugging easy for laptops write a USB or firewire console.

irda too maybe ?

As I said - infrastructure and output hook.. ;)

#21 lore raw
In reply to Andi Kleen

Hi!

Quoted 5 lines
Quoted 5 lines · Dave Jones
Quoted 3 lines

Or you could put down the crackpipe and run a serial console between the two boxes. Or even netconsole would make more sense (and be a lot more reliable).

Quoted 7 lines
Quoted 3 lines

A lot of newer laptops do not have serial ports. While morse code may be a little silly the general purpose hook it needs to be done cleanly is considerably more useful

And how many users and how many kernel hackers are able to decode morse on the fly? Are you going to explain to users
"to debug this you'll need to learn morse" ?

If it is message "could not mount ext2 on /dev/hda2" I guess I could catch enough of it to be usefull.

Quoted 4 lines

I admit I was the on who got this ball running by suggesting it "as an exercise for the reader" in the original panic blink code, but guys this was intended as a JOKE, not serious. Please get over it and don't merge that silly code.

Its not *that* silly. Simple extension of "blink leds on panic".

Pavel

Signature · 2 lines
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
#22 lore raw
Quoted 3 lines · Pavel Machek
Quoted 3 lines

And how many users and how many kernel hackers are able to decode morse on the fly? Are you going to explain to users
"to debug this you'll need to learn morse" ?

You don't need to. All you need is a simple tool where you can toggle the morse code via mouse button or keyboard in and the screen displays the clear text. I'd say you can write this for a Palm (poking the screen with the pen). This is, after all, the 21st century. ;-)

Quoted 2 lines

If it is message "could not mount ext2 on /dev/hda2" I guess I could catch enough of it to be usefull.

Regards
Henning

Signature · 5 lines
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen                  INTERMETA GmbH
[email protected]           +49 9131 50 654 0        http://www.intermeta.de/

  Java, perl, Solaris, Linux, xSP Consulting, Web Services -- hero for hire
        freelance consultant -- Jakarta Turbine Development  -- RHSCLG