irq 19: nobody cared Pid: 0, comm: swapper Not tainted 2.6.35-22-server #35-Ubuntu

Binary package hint: mdadm

My motherboard has a 4 port SATA controller on IRQ 19. If I run my main o/s and swap space on this controller, along with software RAID (mdadm) on the same controller, the system gets into a bit of a tizzy and loses the IRQ of this controller. It will not crash but becomes very unresponsive.

Main o/s and swap is on drive one, port one of mobo SATA. Raid is on drive2, mobo port2 and drive 3, mobo port 3. I create the md0 device then add drive 2, port 2 to the md0 device. This works. I add drive 3 to the md0 device and then the problems occur. I have tested various permutations such as adding a PCI raid card and running one or more of the RAID drives from that PCI card instead. If I run both SATA RAID drives from the PCI controller, this problem does not occur and everything is fine, so I know this is not rerlated to the drives themselves.

If i run one or more SATA RAID drives from the onboard mobo SATA controller, this problem occurs.

[18775.376806] irq 19: nobody cared (try booting with the "irqpoll" option)
[18775.379114] Pid: 0, comm: swapper Not tainted 2.6.35-22-server #35-Ubuntu
[18775.379117] Call Trace:
[18775.379121] <IRQ> [<ffffffff810cb11b>] __report_bad_irq+0x2b/0xa0
[18775.379137] [<ffffffff810cb31c>] note_interrupt+0x18c/0x1d0
[18775.379142] [<ffffffff810cbb1d>] handle_fasteoi_irq+0xdd/0x110
[18775.379148] [<ffffffff8100cb12>] handle_irq+0x22/0x30
[18775.379154] [<ffffffff815a61ec>] do_IRQ+0x6c/0xf0
[18775.379161] [<ffffffff8159edd3>] ret_from_intr+0x0/0x11
[18775.379164] <EOI> [<ffffffff81012c2f>] ? mwait_idle+0x6f/0xd0
[18775.379174] [<ffffffff815a281a>] ? atomic_notifier_call_chain+0x1a/0x20
[18775.379180] [<ffffffff81008d93>] cpu_idle+0xb3/0x110
[18775.379186] [<ffffffff81596763>] start_secondary+0x100/0x102
[18775.379190] handlers:
[18775.381454] [<ffffffff813f3130>] (ata_bmdma_interrupt+0x0/0x240)
[18775.383744] [<ffffffff81417cb0>] (usb_hcd_irq+0x0/0x90)
[18775.386014] Disabling IRQ #19
[18796.080017] ata3: lost interrupt (Status 0x51)
[18796.080041] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[18796.082361] ata3.00: BMDMA stat 0x26, BMDMA stat 0x0, BMDMA stat 0x0, BMDMA stat 0x0, BMDMA stat 0x0
[18796.084826] ata3.00: failed command: READ DMA EXT
[18796.087125] ata3.00: cmd 25/00:80:3f:f6:ce/00:02:59:00:00/e0 tag 0 dma 327680 in
[18796.087127] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x24 (host bus error)
[18796.091974] ata3.00: status: { DRDY }
[18796.094280] ata3: soft resetting link
[18796.470097] ata3.00: configured for UDMA/133
[18796.470104] ata3.00: device reported invalid CHS sector 0
[18796.470114] ata3: EH complete
[18830.021267] ata3: lost interrupt (Status 0x51)
[18830.021290] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[18830.023627] ata3.00: BMDMA stat 0x26, BMDMA stat 0x0, BMDMA stat 0x0, BMDMA stat 0x0, BMDMA stat 0x0
[18830.025972] ata3.00: failed command: READ DMA EXT
[18830.028294] ata3.00: cmd 25/00:00:3f:3a:cf/00:04:59:00:00/e0 tag 0 dma 524288 in
[18830.028295] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x24 (host bus error)
[18830.033010] ata3.00: status: { DRDY }
[18830.035346] ata3: soft resetting link
[18830.370056] ata3.00: configured for UDMA/133
[18830.370063] ata3.00: device reported invalid CHS sector 0
[18830.370074] ata3: EH complete

xxx@hfw1:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
xxx@hfw1:~$ uname -a
Linux hfw1 2.6.35-22-server #35-Ubuntu SMP Sat Oct 16 22:02:33 UTC 2010 x86_64 GNU/Linux
xxx@hfw1:~$