[Voyage-linux] Interrupt Problem with COM3 and COM4

[Dan Boss]

Hi

I try to run 4 serial lines (COM1 to COM4) on a IEI KINO-945GSE under Voyage Linux 0.7.0.
Serial lines COM1 and COM2 work without a problem but as soon as my application wants to access the devices /dev/ttyS2 and /dev/ttyS3 I get the following kernel message:

[   32.562273] irq 10: nobody cared (try booting with the "irqpoll" option)
[   32.563011] Pid: 2887, comm: acid Not tainted 2.6.32-voyage #1
[   32.563011] Call Trace:
[   32.563011]  [<c103cdc4>] __report_bad_irq+0x2e/0x6f
[   32.563011]  [<c103cef2>] note_interrupt+0xed/0x14b
[   32.563011]  [<c103d599>] handle_level_irq+0x8f/0xe1
[   32.563011]  [<c100412d>] handle_irq+0x21/0x28
[   32.563011]  [<c1003ec9>] do_IRQ+0x33/0x70
[   32.563011]  [<c1002fc9>] common_interrupt+0x29/0x30
[   32.563011]  [<c101ac2a>] ? __do_softirq+0x34/0xca
[   32.563011]  [<c101ace5>] do_softirq+0x25/0x2a
[   32.563011]  [<c101ae08>] irq_exit+0x28/0x61
[   32.563011]  [<c1003ef1>] do_IRQ+0x5b/0x70
[   32.563011]  [<c1002fc9>] common_interrupt+0x29/0x30
[   32.563011]  [<c103007b>] ? tick_nohz_restart_sched_tick+0x1d/0x1a3
[   32.563011]  [<c103c78c>] ? __setup_irq+0x1f1/0x29e
[   32.563011]  [<c103c8fe>] request_threaded_irq+0xc5/0xf2
[   32.563011]  [<c119fdb8>] ? serial8250_interrupt+0x0/0xd5
[   32.563011]  [<c119fa79>] serial8250_startup+0x444/0x5ab
[   32.563011]  [<c119c5a2>] uart_startup+0x6b/0x140
[   32.563011]  [<c119d080>] uart_open+0x103/0x345
[   32.563011]  [<c1187ff3>] ? tty_init_dev+0x106/0x14b
[   32.563011]  [<c11882cb>] tty_open+0x293/0x37c
[   32.563011]  [<c106323a>] chrdev_open+0x15e/0x175
[   32.563011]  [<c105f8e2>] __dentry_open+0x12b/0x218
[   32.563011]  [<c105fa68>] nameidata_to_filp+0x2b/0x42
[   32.563011]  [<c10630dc>] ? chrdev_open+0x0/0x175
[   32.563011]  [<c106a6bc>] do_filp_open+0x3bb/0x716
[   32.563011]  [<c1188ee9>] ? n_tty_ioctl+0x0/0xa3
[   32.563011]  [<c1187a2b>] ? tty_ioctl+0x6f8/0x71b
[   32.563011]  [<c1072527>] ? alloc_fd+0x5c/0xe0
[   32.563011]  [<c105f6b5>] do_sys_open+0x4a/0xed
[   32.563011]  [<c105f79a>] sys_open+0x1e/0x26
[   32.563011]  [<c10029b5>] syscall_call+0x7/0xb
[   32.563011] handlers:
[   32.563011] [<c119fdb8>] (serial8250_interrupt+0x0/0xd5)
[   32.563011] Disabling IRQ #10

When trying to receive data through the serial line a lot of it is lost.
I already tried the bootoption "irqpoll" with the result, that the kernel message no longer shows up, but the data received is still corrupt.

I checked the IRQs in the Bios (IRQ 10 for COM3, IRQ 11 for COM4) and they are also detected this way during kernel boot, so no obvious error here.

Is anybody familiar with this or a similar problem and can give me some pointers for a possible solution?

Thank you

Dan Boss