[coreboot] bug report on dbm690t

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Tue Feb 2 13:19:25 CET 2010


On 02.02.2010 05:08, Bao, Zheng wrote:
> The SATA can not be set correctly in kernel stage if the coreboot is
> built in Kconfig way.
> scsi0 : ahci
> scsi1 : ahci
> scsi2 : ahci
> scsi3 : ahci
> ata1: SATA max UDMA/133 abar m1024 at 0xfc309000 port 0xfc309100 irq 16
> ata2: SATA max UDMA/133 abar m1024 at 0xfc309000 port 0xfc309180 irq 16
> ata3: SATA max UDMA/133 abar m1024 at 0xfc309000 port 0xfc309200 irq 16
> ata4: SATA max UDMA/133 abar m1024 at 0xfc309000 port 0xfc309280 irq 16
> ata2: SATA link down (SStatus 0 SControl 300)
> ata3: SATA link down (SStatus 0 SControl 300)
> ata4: SATA link down (SStatus 0 SControl 300)
> ata1: softreset failed (device not ready)
> ata1: applying SB600 PMP SRST workaround and retrying
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: softreset failed (device not ready)
> ata1: applying SB600 PMP SRST workaround and retrying
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: limiting SATA link speed to 1.5 Gbps
> ata1: softreset failed (device not ready)
> ata1: applying SB600 PMP SRST workaround and retrying
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: softreset failed (device not ready)
> ata1: applying SB600 PMP SRST workaround and retrying
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>   

I get similar errors if my Asus M2A-VM board has 4 GB RAM (older
coreboot revision, buildtarget). Maybe this is related.

ahci 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024 at 0xfc409000 port 0xfc409100 irq 22
ata2: SATA max UDMA/133 abar m1024 at 0xfc409000 port 0xfc409180 irq 22
ata3: SATA max UDMA/133 abar m1024 at 0xfc409000 port 0xfc409200 irq 22
ata4: SATA max UDMA/133 abar m1024 at 0xfc409000 port 0xfc409280 irq 22
ata1: softreset failed (device not ready)
ata1: failed due to HW bug, retry pmp=0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata1: softreset failed (device not ready)
ata1: failed due to HW bug, retry pmp=0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)

Did you manage to track down the 4 GB issue? I didn't see any mails from
you after January 2009 about this topic.

Regards,
Carl-Daniel

-- 
Developer quote of the year:
"We are juggling too many chainsaws and flaming arrows and tigers."





More information about the coreboot mailing list