Thanks for the help. I was wondering, this error didn't start happening until
I installed the scsi drive. Now the message says that the scsi drive is
merely reporting the problem. Is it possible that the controler is wrong and
that it IS causing the error; or is it that nothing else reports such things?
One other thing: the controler that is reporting this is 'scsi1'. I only have
one scsi device in my system.... unless you want to consider the cdroms as
scsi devices. If that is so then I have 3. Or is scsi1 the first device as
opposed to scsi0?
On Wednesday 25 August 2004 12:39 am, Robert Ambrose wrote:
> First, I hope you have backups, MondoRescue is your friend.
>
> A common technique used to figure out your PCI problem is called hit,
> miss and guess ;-). Remove all hardware from the system until you have
> the bare essentials to run your system. If you still have the errors,
> you will have to play the swap game until the errors go away. If a bare
> system doesn't have the errors, put back cards one at a time until the
> errors return.
>
> You should be able to get the config file for cups by doing 'strings
> /usr/sbin/cupsd | grep cupsd.conf'.
>
> rna
>
> On Tue, 2004-08-24 at 20:26, Michael Havens wrote:
> > On Tuesday 24 August 2004 12:01 pm, Robert Ambrose wrote:
> > > Maybe you don't have CUPS installed. Check out what has 631 open by
> > > doing a 'lsof -ni :631'.
> >
> > I ran it and it returned empty. That means it issn't installed? No that
> > can't be it. 'ps -aux' lists it (/usr/sbin/cupsd) as running.
> >
> > Wait. I turned off all the logging yesterday and I just checked dmesg and
> > the printer thingy isn't happening but the evil hacker thing is still
> > happening.
> >
> > Another thing that still needs a resolution is that I still am getting
> > the message:
> >
> > scsi1: PCI error Interrupt at seqaddr = 0x9
> > scsi1: Data Parit Error Detected durring address or write data phase.
> > scsi1: WARNING WARNING WARNING
> > scsi1: Too many PCI parity errors observed as a target.
> > scsi1: Some device on this bus is generating bad parity.
> > scsi1: This is an error *observed by*, not *generated by*, this
> > controller. scsi1: PCI parity checking has been disabled.
> > scsi1: WARNING WARNING WARNING
> >
> > The two lines then repeat but the 9 changes to an 8 or a 7.
> >
> > So I suppose this means that one of my IDE devices is failing and that
> > the scsi controller detected it. (this error first started displaying
> > about two years ago when I installed a scsi controller). Any idea how to
> > figure out which one is failing? I think that I would just like to turn
> > this scsi controller feature off (if I can) if this is this old machines
> > desperate fight to stay alive. How would I go about doing that?
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
--
<:-)Mike(-:>
This message has been scanned for viruses by the VEI Internet
Automatic Email Spam and Virus Scanner, and is believed to be free of spam or viruses.
Please report spam to
spamtrap@vei.net. If you would like 98.9 % spam blocked from your
E-mail then go to VEI Internet for details. Anti-spam/Anti-virus is FREE with every account.
http://www.vei.net/
mailtospamtrap@vei.net
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)