# setserial /dev/ttyS0 auto_irq skip_test autoconfig
# setserial /dev/ttyS1 auto_irq skip_test autoconfig
# setserial -bg /dev/ttyS0 /dev/ttyS1
/dev/ttyS0 at 0x03f8 (irq = 0) is a 16550A
/dev/ttyS1 at 0x02f8 (irq = 0) is a 16550A
with the result that characters sent into the serial port don't wake a
reading process up. Given that my mouse is on ttyS0, this is (cough)
inconvenient. If I disable the calls to setserial then things seem to
work fine. This is on a dual PPro SMP machine.
The reason I'm running setserial in the first place is that on some
machines the serial ports don't use IRQs 4 and 3 (I have ttyS2 on
IRQ 5). So I need setserial to work. Disabling it is a temporary
hack.
This problem may be related to a problem I reported earlier with
2.1.10x on a UP machine, where setserial could hang (control-C would
kill it). I never got any response, though. I suppose this is the same
problem getting worse.
Does anybody have any idea what's going on here?
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html