> On Tue, 30 Nov 1999, Jim Woodward wrote:
>
> > This may or may not be a kernel issue, however
> >
> > Whenever I invoke zgv, I get on the console:
> > sym53c810a-0: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0
>
> It may happen that this application access the PCI configuration space of
> the chip far beyong the pre-defined header area and hits the range that
> has side effects (IO registers mapped to config space).
> Such an attack confuses a lot the chip and the driver, btw.
> If I am right, the only solution is to teach zgv about the PCI specs.;)
Actually I think zgv does something weird in that regard, when running it
on a VESA Local Bus, came up with all sorts of weird PCI probing errors.
I'll have a look through the source of it and see what it may be.
Regards, Jim
-- my name : Jim AJ Woodward my realm : http://www.jim.southcom.com.au my e-mail : jim@jim.southcom.com.au
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/