Our hardware may be generating PCI parity Errors. The end result is that
the system locks up hard. Is there a way of detecting that our device has
generated a PCI parity error at the driver level? And is it possible to
keep the system from freezing when this happens?
Josh
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Did you check the Status register in the Config space for the PE bit -
detected Parity Error.
Paul Lever
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Monday, May 21, 2001 1:55 PM
Subject: [ntdev] PCI parity errors under 2000
> Our hardware may be generating PCI parity Errors. The end result is that
> the system locks up hard. Is there a way of detecting that our device has
> generated a PCI parity error at the driver level? And is it possible to
> keep the system from freezing when this happens?
>
> Josh
>
> —
> You are currently subscribed to ntdev as: xxxxx@home.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
On 05/21/01, ““Paul Lever” ” wrote:
> Did you check the Status register in the Config space for the PE bit -
> detected Parity Error.
>
We’ve looked at the status register, it’s hasn’t been set, but I’m not sure
if that is set when we generate a parity error, or if we detect a parity
error.
Josh
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com