[fm-discuss] many fmd errors on T2000

[Gavin Maltby]

Hi Robert,

On 06/19/06 10:57, Robert Milkowski wrote:
> Hi.
> 
> snv_39 sun4v (T2000)
> 
> What are below errors about?
[cut]
> bash-3.00# fmdump -e| tail -10
> Jun 19 08:52:08.9100 ereport.io.fire.pec.re
> Jun 19 08:52:08.9116 ereport.io.fire.pec.btp
> Jun 19 10:32:06.4630 ereport.io.fire.pec.re
> Jun 19 10:32:06.4638 ereport.io.fire.pec.btp
> Jun 19 10:32:37.5821 ereport.io.fire.pec.re
> Jun 19 10:32:37.5828 ereport.io.fire.pec.btp
> Jun 19 11:04:33.9641 ereport.io.fire.pec.re
> Jun 19 11:04:33.9648 ereport.io.fire.pec.btp
> Jun 19 11:07:04.6300 ereport.io.fire.pec.re
> Jun 19 11:07:04.6316 ereport.io.fire.pec.btp
> bash-3.00#

My pcie-enabled colleague says:

	These are correctable errors on the PCIe link (receiver errors and Bad TLPs).
	Sounds like a bad link. The transactions are being retried successfully (for now).

	Actually the spec specifically says that if the Physical Layer detects a
	receiver error, then the Link Layer must not also report the error as a bad TLP,
	so there looks to be a chip error handling bug too.

All those ereports should have resulted in some diagnosis.  What does
'fmadm faulty' report, and what does 'fmdump -v' show?

[cut]

Gavin

-- 
Gavin Maltby, Solaris Kernel Development.