Comment 14 for bug 595321

I've tested the daily iso 9-16-10 and drives still fail to be detected.
The controller is detected and up
from dmesg log
[ 2.376037] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2.384049] ata1.00: both IDENTIFYs aborted, assuming NODEV
[ 2.556648] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x57d @ 1, addr 00:04:4b:80:80:03
[ 2.556714] forcedeth 0000:00:04.0: timirq lnktim desc-v1
[ 2.556900] pata_amd 0000:00:09.0: version 0.4.1
[ 2.556956] pata_amd 0000:00:09.0: setting latency timer to 64
[ 2.557141] scsi4 : pata_amd
[ 2.557312] scsi5 : pata_amd
[ 2.558221] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[ 2.558279] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[ 2.704035] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2.712200] ata2.00: both IDENTIFYs aborted, assuming NODEV

from debug log
Sep 17 09:51:51 maverick kernel: [ 2.042014] sata_sil 0000:01:0b.0: version 2.4
Sep 17 09:51:51 maverick kernel: [ 2.042318] alloc irq_desc for 19 on node -1
Sep 17 09:51:51 maverick kernel: [ 2.042320] alloc kstat_irqs on node -1
Sep 17 09:51:51 maverick kernel: [ 2.384049] ata1.00: both IDENTIFYs aborted, assuming NODEV
Sep 17 09:51:51 maverick kernel: [ 2.556900] pata_amd 0000:00:09.0: version 0.4.1
Sep 17 09:51:51 maverick kernel: [ 2.556956] pata_amd 0000:00:09.0: setting latency timer to 64
Sep 17 09:51:51 maverick kernel: [ 2.712200] ata2.00: both IDENTIFYs aborted, assuming NODEV

Still no problems with previous kernels installed or booted from iso.
I have been digging in change logs of all kinds of packages and cannot seem to find the culprit.
What other information can I provide to help track down the cause of this?