>>
>> ahc: Data Parity Error Detected during address or write data phase
>> PCI Interupt at seqaddr=0x8 <- this also alternates with 0x9o
>>
>
>there seem to be some issues with the ahc driver in 4.3-BETA and BETA2
>see the "ahc invalidating pack" thread for some details.
>some fixes were just committed so we all need to do a cvsup and
>recompile. (with a older kernel, of course)
Nothing was committed that would affect reported PCI parity errors.
It may be that your chipset just doesn't generate parity correctly.
It may also be that the card edge is dirty or the slot is. Hard
to say. The parity error reporting can be disabled if necessary.
I'll look into adding a device flag for that in the near future.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
