Re: Adaptec 29160N errors
here are the errors from the messages log. This ONLY happened when A) a device was connected to the Adaptec 29160N and B) when the device was being used by dump. According the the replies I am afraid the problem may be related to the MB.. And ideas on how to trouble shoot it? For some reason this error no longer occurs with the AHA-2940. Could it be some IRQ conflict? I know that the SCSI controller used IRQ 11, as do alot of the other devices on the system.. ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x8 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x9 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x82 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: WARNING WARNING WARNING WARNING ns1 kernel: ahc0: Too many PCI parity errors observed as a target. ns1 kernel: ahc0: Some device on this bus is generating bad parity. ns1 kernel: ahc0: This is an error *observed by*, not *generated by*, this controller. ns1 kernel: ahc0: PCI parity error checking has been disabled. ns1 kernel: ahc0: WARNING WARNING WARNING WARNING ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adaptec 29160N errors
> The controller is complaining that some device in your system is > generating > PCI transactions that cannot be safely decoded because they contain parity > errors. Just moving the 160 card won't make this situation go away. You > need to find the source of these errors. Otherwise, you might as well > live with the message in your dmesg log and go on with life. > At the time of the errors there was and still is only 1 device on the controller. I have tried 2 different devices 1 internal 1 external as well as a handful of different cables. > Again, this has nothing to do with the SCSI controller, the devices > attached to it, or anything SCSI specific. Some other PCI device is > causing the problem. > the only other PCI device in the machine is the NIC. > > The BIOS for this card may be configuring it to ignore PCI parity > errors. > That was my guess as well. The 29160N has parity set to Auto, the AHA-2940 has no such option. But I have read about this issue and the 29160N cards with any NIX system, or some BSD system. Most of the issues were resolved by moving the card from one PCI slot to another. My MAIN concern is that the card controlls my Tape Backup Drive sa0... The last thing I want to have happen is all my data on the tapes be corrupt and/or un-Readable due to the parity errors ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
