|
Description
|
If a driver starts by reporting "service.unaffected" ereports and then, within 5 seconds, decides it can no longer recover and reports "service.lost" ereports, the diagnosis rules can get confused. They treat both service.unaffected and service.lost as part of the same "noimpact" case (waiting for a service.restored to match the service.lost). Then the service.repaired doesn't turn up and the case is considered undiagnosable. The same thing occurs if the state changes from unaffected to degraded or from degraded to lost.
The easiest fix is probably to say that service.degraded and service.unaffected errors can be expected as a symptom of a service.lost fault and that service.unaffected errors can be expected as a symptom of a service.degraded fault.
|
