All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael P. Carel" <mikecarel@teamglac.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Address or Write Phase Parity Error in  Adaptec Ultra320(29320)
Date: Mon, 14 Apr 2003 12:45:46 +0800	[thread overview]
Message-ID: <008501c30240$b7049840$8601a8c0@teamglac.com> (raw)
In-Reply-To: 2574772704.1050290648@aslan.scsiguy.com

changing slots doesnt change anything but removing the network make the scsi
work fine, but i need a network in this machine. What should i do?

----- Original Message -----
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "Michael P. Carel" <mikecarel@teamglac.com>
Sent: Monday, April 14, 2003 11:24 AM
Subject: Re: Address or Write Phase Parity Error in Adaptec Ultra320(29320)


> > attached was the dmesg and the lspci output. I'm using EPOX 4G4A with
Intel
> > chipset that have  a 32bit PCI slots.
>
> Some things to try:
>
> 1) Do you still get these messages when drivers for most other peripherals
> are not loaded (no sound, no ethernet, no ide, etc).
>
> 2) Does the behavior change when you change slots?
>
> I don't have a lot of experience with the 845xx chipsets, but you may
> be able to avoid the problem by moving the 29320 to a bus that is not
> getting strafed by some device sending out PCI transactions with bad
> parity.
>
> --
> Justin


  parent reply	other threads:[~2003-04-14  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14  1:59 Address or Write Phase Parity Error in Adaptec Ultra320(29320) Michael P. Carel
2003-04-14  2:37 ` Justin T. Gibbs
2003-04-14  2:43   ` Michael P. Carel
     [not found]     ` <2574772704.1050290648@aslan.scsiguy.com>
2003-04-14  4:45       ` Michael P. Carel [this message]
2003-04-14  5:35         ` Michael P. Carel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008501c30240$b7049840$8601a8c0@teamglac.com' \
    --to=mikecarel@teamglac.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.