Skip to contentSkip to conversation

How to hang 2.6.9 using serial port and FB console

DISCUSSION Karel Kulhavy 3 participants 6 messages Dec 26, 2004 – Jan 15, 2005 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hello

1) Obtain gentoo LiveCD 2004.3 which contains kernel 2.6.9-gentoo-r1
2) Obtain remote controller "YAMAHA REMOTE CONTROL TRANSMITTER RCX" from "YAMAHA NATURAL SOUND STEREO RECEIVER RX-360 =RS"
3) Obtain an IrDA dongle based on datasheet circuit of HSDL3612
4) Obtain a motherboard with IrDA connector
5) Enable IrDA in BIOS, set up RX active Lo and TX active Hi and Full Duplex (on my board, FIC VA503+ with 400MHz Athlon it was COM2 alias /dev/ttyS1)
6) Boot up the "gentoo" kernel from the LiveCD
7) Do stty -F /dev/ttyS1 ispeed 19200 ospeed 19200
8) Do hexdump /dev/ttyS1 on console 2 (those without the fancy graphics)
9) Press couple of keys on the remote control until the hexdump starts spewing tons of characters continuously even when you don't press anything. Switch to console 3 and back. Nothing happens.
10) Break the hexdump and run the cat again on console 1 (with fancy graphics)
11) Press keys on remote control until hexdump starts spewing chars continuously
12) Switch to console 3
13) Try to switch back to console 1. The system stops responding:
Action Does user notice anything?
---------------------------------------

numlock      no
capslock     no
scrolllock   no
ctrl-alt-del no
alt-sysrq-a  no
alt-sysrq-u  no
alt-sysrq-b  reboot

The board used and the hardware in the PC is for a long time in usage and don't have any observable problems.

Cl<

A message that is not in the archive (sent off-list or not yet received): 20041226145334.GC1668@gallifrey

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): 20041226155350.GD1668@gallifrey

#4 lore raw
Quoted 8 lines · Dr. David Alan Gilbert
Quoted 5 lines · * Karel Kulhavy ([email protected]) wrote:
Quoted 2 lines · Dr. David Alan Gilbert

Hi Karel,
I wonder - is the board sending a 'break' signal to the PC? I just

What board do you mean?

Your IR interface board.

The IR interface isn't a board. It's a HSDL3612 with 2 capacitors and one resistor soldered in a box according to the recommended wiring from datasheet, so technically, it's not a board, but an airwire construction ;-)

However it is not sending breaks, but rather various characters. As the kernel seems to be set internally for echo cahracters going into the computer on the transmit line again, and the characters are echoed by the infrared receiver during transmission too, a character stream cycles infinitely there.

However kernel shouldn't hang even if you wired the serial input to an alien spacecraft.

CL<

#5 lore raw
Quoted 7 lines · Karel Kulhavy

However it is not sending breaks, but rather various characters. As the kernel seems to be set internally for echo cahracters going into the computer on the transmit line again, and the characters are echoed by the infrared receiver during transmission too, a character stream cycles infinitely there.

However kernel shouldn't hang even if you wired the serial input to an alien spacecraft.

How do you know if it's the serial that's causing the hang rather than the virtual console subsystem?

Your original description seems to imply that the machine only hung after you switched from VC1 to VC3, and then you found you couldn't switch back to VC1. To me, that sounds virtual console related rather than serial related. Especially if you can reproduce it at this exact point in time every time.

Have you tried sysrq-p or sysrq-t to get a trace/thread info from the kernel?

Signature · 4 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core
#6 lore raw
In reply to a message not in the archive
Quoted 4 lines · Dr. David Alan Gilbert

Hi Karel,
I wonder - is the board sending a 'break' signal to the PC? I just
remember years ago you could almsot lock machines up by constantly sending break.

But in this case the kernel doesn't care if you run it on a console without a fancy background picture and hangs when you run it on a fancy background picture.

The picture is what seems to be evil here.

Cl<

#7 lore raw

I found out another bit of information:

When the kernel is hanged up and I remove the infra dongle (so that nothing is sent towards the computer anymore for sure), the kernel stays hanging.

This is therefore a final proof that it is not caused by sending breaks. Dongle that is not present can't send breaks anymore ;-)

Cl<

Quoted 18 lines · Karel Kulhavy
Quoted 4 lines · Dr. David Alan Gilbert

Hi Karel,
I wonder - is the board sending a 'break' signal to the PC? I just
remember years ago you could almsot lock machines up by constantly sending break.

But in this case the kernel doesn't care if you run it on a console without a fancy background picture and hangs when you run it on a fancy background picture.

The picture is what seems to be evil here.

Cl<
-
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/

#8 lore raw
In reply to Karel Kulhavy

Hi!

Quoted 9 lines
Quoted 3 lines

I wonder - is the board sending a 'break' signal to the PC? I just
remember years ago you could almsot lock machines up by constantly sending break.

But in this case the kernel doesn't care if you run it on a console without a fancy background picture and hangs when you run it on a fancy background picture.

The picture is what seems to be evil here.

Picture is not in vanilla kernel => complain to gentoo.
Pavel

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!