Re: serial8250 madness

[Alan Cox]

> ttyS0 works fine. Can get grub output, kernel boot and console via ttyS0 
> as I wanted.
> ttyS1 doesn't work at all. It's detected, enabled in the bios etc etc 
> but just doesn't work at all.

You don't give much information but if it seems to be non working then I
would look hard at the IRQ/IO reported

> Machine B
> 
> ttyS0 and ttyS1 will both receive, but neither will send. Go figure. 
> Tested using a null modem cable, setserial and cu against the known good 
> machine above.

Boggle - what flow control wiring have you done ?

> Machine C
> 
> Grub and kernel outputs fine during boot, right up til the serial8250 
> output appears in the kernel log, at which point it then prints 'LSR 
> safety check engaged' and reboots.
> Tried again without the console=ttyS0,57600 kernel parameter and it 
> boots OK but starts printing the 'LSR...' message again as soon as 
> agetty tries to attach to ttyS0. Doesn't reboot though...
> 
> The Machines are all amd64, various motherboards, identical distros 
> using 2.6.28.1 kernel.
> Either I have a particularly motley collection of kit, or the serial 
> code is in a pretty bad way.

It is maintained and should be pretty solid. Seria console is one of the
less used bits but when it gets broken people do jump up and down and
shout about it.

The big outstanding bug I know about is the incompatibility between the
PnP 8250 drivers and serial console - that may be your machine C case.
That one is rather hard to fix so on the long rather than short term hit
list.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/