Hi,
I do not know if it is related to 2.1.120-pre3, but this
can appear if the two serial ports are on the same IRQ, or
if another board maintains the IRQ line active.
Also, you have a two processor machine, the two "setserial"
may be done in parallel - not nice for IRQ probing...
Why did you add the "skip_test" option ?
What happens if you compile the kernel with "SERIAL_DETECT_IRQ"
(then the driver initialise all serial ports - and clear IRQ lines -
*before* autodetecting the IRQs, and does that sequencially for
each lines).
Then you can remove the setserial lines from your startup scripts,
probing for IRQ is basically unsafe but it is better to do that
at kernel startup than when a lot of tasks are running in 'init'.
The safest is always to do "setserial /dev/ttyS0 irq 4".
> Does anybody have any idea what's going on here?
Just ideas... nothing as interresting as a Penguin beer!
Etienne.
-- -- The world belong to its organizer.- 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