|
Description
|
Some error messages logged by ahci driver are too cryptic:
static void
ahci_log_fatal_error_message(ahci_ctl_t *ahci_ctlp, uint8_t port,
uint32_t intr_status)
{
#ifndef __lock_lint
_NOTE(ARGUNUSED(ahci_ctlp))
#endif
if (intr_status & AHCI_INTR_STATUS_IFS)
cmn_err(CE_NOTE, "!ahci port %d has interface fatal "
"error", port);
if (intr_status & AHCI_INTR_STATUS_HBDS)
cmn_err(CE_NOTE, "!ahci port %d has bus data error", port);
if (intr_status & AHCI_INTR_STATUS_HBFS)
cmn_err(CE_NOTE, "!ahci port %d has bus fatal error", port);
if (intr_status & AHCI_INTR_STATUS_TFES)
cmn_err(CE_NOTE, "!ahci port %d has task file error", port);
cmn_err(CE_NOTE, "!ahci port %d is trying to do error "
"recovery", port);
}
They do not provide information other than the fact that an error happen, but even than, it is not clear what they are referring to:
what bus?
what task file error (device)?
what kind of interface error?
These messages will eventually be replaced by FMA reports, but until then they should be more usable in the sense that they should hint what the operator may have to fix.
|
