Hi!
I wonder if my
Bus 0, device 9, function 0:
SCSI storage controller: Adaptec AHA-7850 (rev 3).
IRQ 11.
Master Capable. Latency=32. Min Gnt=4.Max Lat=4.
I/O at 0xa000 [0xa0ff].
Non-prefetchable 32 bit memory at 0xe7001000 [0xe7001fff].
is broken or the aic7xxx driver in linux-2.4.20-pre7-ac3?
The modul loads fine, the cdrom seems to work properly, though,
but this messages appears in my
message.log:
==> /var/log/syslog <==
Sep 23 19:32:23 sexmachine kernel: scsi1: PCI error Interrupt at seqaddr
= 0x9
Sep 23 19:32:23 sexmachine kernel: scsi1: Data Parity Error Detected
during address or write data phase
several times a minute. The aic7xxx_old produces no errorr messages...
Konsti
--
Kletschke & Uhlig GbR:
http://www.ku-gbr.de
> Hi!
>
> I wonder if my
>
> Bus 0, device 9, function 0:
> SCSI storage controller: Adaptec AHA-7850 (rev 3).
...
> is broken or the aic7xxx driver in linux-2.4.20-pre7-ac3?
>
> The modul loads fine, the cdrom seems to work properly, though,
> but this messages appears in my
> message.log:
>
> ==> /var/log/syslog <==
> Sep 23 19:32:23 sexmachine kernel: scsi1: PCI error Interrupt at seqaddr
> = 0x9
> Sep 23 19:32:23 sexmachine kernel: scsi1: Data Parity Error Detected
> during address or write data phase
>
> several times a minute. The aic7xxx_old produces no errorr messages...
On some motherboards with some chipsets, you can get these messages if
another busmaster (say an IDE drive or a sound card) is hogging the bus.
Usually this is with a VIA chipset. Its not clear why the aic7xxx_old
driver would behave differently other than it disables memory write
and invalidate PCI transactions on this chip. The new driver doesn't
need that work around.
As to wether it is safe or not, well our investigation into these issues
has shown that the parity errors are real, but it is the parity that
is at fault. It is hard to say if that is the case for your MB or not.
Can you provide, in private email, a full lspci dump?
Thanks,
Justin