There are several chipsets that seem to elicit PCI parity error interrupts
from the aic7xxx chips. The question that I've never been able to answer,
however, is if the parity errors are real or not. We don't have any hardware
that seems to trigger this problem otherwise I would simply stick on our
PCI bus analyzer and figure this out for good. What may help me is to know
the chipset used on your system. A dmesg and an lspci -v dump should give
me that info.

As for the dmesg, you will need to get it right after boot, or capture
the boot messages from /var/log/messages or via a serial console. I'm looking
for the driver initialization messages, not the error messages. 8-)
--
Justin

I tried installing the aic7xxx-6.2.28 rpm and got the following message:
[root@kenyatta rpm]# rpm -Uvh aic7xxx-6.2.28-rh80.i686.rpm
Preparing... ########################################### [100%]
package aic7xxx-6.2.28-1 is intended for a i686 architecture
Since I have a K6 CPU I suspect that I need an RPM for the i586 architecture.
Unfortunately, another bug, #81703, makes my floppy drive inaccessible under
RH8.0 so I can't use a driver disk. Would it be possible to get an i586 version
of the aic7xxx-6.2.28 RPM ?
Ken Riley
khriley@ameritech.net

Created attachment 89544[details]
messages during aic7xxx-6.2.28-rh80.i686.rpm install
command line was "rpm -Uvh --ignorearch aic7xxx-6.2.28-rh80.i686.rpm"
For some reason, the module didn't install to two of my kernels.
See attachment nohup.1 for error messages during rpm install.
Ken Riley
khriley@ameritech.net

Can you see if you are sharing interrupts between the 29160 and some other
device. The change in 6.2.28 should disable the generation of PCI parity
error interrupts, but my guess is that the parity error status is still
registered by the controller. In that case, the only time we would notice
the parity error is during the processing of a shared interrupt request where
no other status is set in the chip. the output from 'cat /proc/interrupts'
should tell you if the interrupt is shared.

Can you update your PCI listing by using "lspci -vv" after booting
with the new driver? The extra verbosity will decode all of the bits
in the command register, including the parity error enable bit.
Thanks!

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note

You need to
log in
before you can comment on or make changes to this bug.