Ric Wheeler wrote:
> c001n01: 0: [  OK  ]
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x2000000f)
> ata3: spurious SDB FIS 004040a1:10000000 ap->qc_active=2000000f 
> qc_active=2000000f
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0xfffc0)
> ata1: spurious SDB FIS 004040a1:00000020 ap->qc_active=000fffc0 
> qc_active=000fffc0
> ata2: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x7fffff3f)
> ata2: spurious SDB FIS 004040a1:00000080 ap->qc_active=7fffff3f 
> qc_active=7fffff3f
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x7fffff9f)
> ata1: spurious SDB FIS 004040a1:00000040 ap->qc_active=7fffff9f 
> qc_active=7fffff9f
> c001n03: 0: [  OK  ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x7ffe7fff)
> ata1: spurious SDB FIS 004040a1:00010000 ap->qc_active=7ffe7fff 
> qc_active=7ffe7fff
> c001n04: 0: [  OK  ]
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x31)
> ata3: spurious SDB FIS 004040a1:00000008 ap->qc_active=00000031 
> qc_active=00000031
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x7fff800f)
> ata3: spurious SDB FIS 004040a1:00004000 ap->qc_active=7fff800f 
> qc_active=7fff800f
> c001n06: 1: [ FAIL ]
> c001n07: 0: [  OK  ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x7ffffcff)
> ata1: spurious SDB FIS 004040a1:00000200 ap->qc_active=7ffffcff 
> qc_active=7ffffcff
> c001n08: 0: [  OK  ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 
> 0x4fffffff)
> ata1: spurious SDB FIS 004040a1:20000000 ap->qc_active=4fffffff 
> qc_active=4fffffff

Hmmm.. The drive is issuing SDB FIS which completes already completed 
tags.  This could be dangerous.  Depending on timing, it might end up 
finishing a command which occupied the slot which hasn't been processed 
yet.  If a drive does this, NCQ shouldn't be enabled for it.  Can you 
post full boot dmesg?

I'm attaching slightly modified version of the debug patch just in case. 
  It will probably show the same thing.

-- 
tejun