public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Rodrigo Severo <rodrigo@fabricadeideias.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Adaptec 29320LPE errors on boot
Date: Wed, 05 Mar 2008 09:55:23 -0600	[thread overview]
Message-ID: <1204732523.3047.27.camel@localhost.localdomain> (raw)
In-Reply-To: <a7108f870803050742x6a960bf4sed894208a5fb3931@mail.gmail.com>

On Wed, 2008-03-05 at 12:42 -0300, Rodrigo Severo wrote:
> Hi,
> 
> 
> I have this Adaptec 29320LPE SCSI board (used the aic79xx driver)
> which give several errors during boot time, just after it recognizes
> the HDs connected to it.
> 
> If I remove the SCSI HD there are no SCSI errors.
> 
> The very first error messages have scrolled up and I don't know how to
> get to them (is there a way?)

If you can get it to boot (say to a ramdisk with a shell) then dmesg
gives them ... otherwise you need a serial console.

>  but here is the transcript of what I can
> see:
> 
> scsi0: hwerrint, Sequencer Parity Error
> scsi0: hwerrint, Data-path Parity Error
> scsi0: hwerrint, Scratch or SCB Memory Parity Error
> scsi0: hwerrint, CIOBUS Parity Error

That's a pretty comprehensive sequence of parity errors.  Assuming
they're the root cause rather than something caused by the first error:
best case, you just need a better cable or termination; worst case, your
card is actually hosed in its internal data path.

James



  reply	other threads:[~2008-03-05 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 15:42 Adaptec 29320LPE errors on boot Rodrigo Severo
2008-03-05 15:55 ` James Bottomley [this message]
2008-03-05 16:26   ` Rodrigo Severo
     [not found] ` <532ABFBDAAC3A34EB12EBA6CEC2838F4831D6BEF@ADPE2K703.adaptec.com>
2008-03-05 16:26   ` Rodrigo Severo
2008-03-05 16:32     ` James Bottomley
2008-03-05 16:52       ` Rodrigo Severo
2008-03-05 17:10         ` James Bottomley
2008-03-05 19:14           ` Rodrigo Severo
2008-03-05 17:11         ` Matthew Wilcox
2008-03-05 19:14           ` Rodrigo Severo

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=1204732523.3047.27.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rodrigo@fabricadeideias.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox