All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Bouthors <guizmow@nbi.fr>
To: linux-scsi@vger.kernel.org
Subject: Strange problem from 2.4.9 to 2.4.20
Date: Mon, 02 Aug 2004 09:59:54 +0200	[thread overview]
Message-ID: <410DF47A.1060501@nbi.fr> (raw)

Hi all,

I hope this is not a FAQ, I tried to look in the archives but couldn't 
find anything relevant :
I have a problem with a change of kernel. The machine is a dell with 2 
internal SCSI
drives and an external RAID array the machine has 4 Adaptec controlers 
and evetything
works fine with kernel 2.4.9 from Redhat. For testing purpose I compiled 
a 2.4.20 and
when I boot I get the following message :

(scsi2:A:3): 80.000MB/s transfers (40.000MHz DT, offset 31, 16bit)
(scsi2:A:3:0): parity error detected in Command phase. SEQADDR(0x1a2) 
SCSIRATE(0xc3)
  CRC Value Mismatch
  No terminal CRC packet recevied
  Illegal CRC packet request
  Unexpected non-DT Data Phase
scsi2:A:3: Missed busfree. Lastphase = 0xe0, Curphase = 0x0
(scsi2:A:3:0): parity error detected in Command phase. SEQADDR(0x1a2) 
SCSIRATE(0xc3)
  CRC Value Mismatch
  No terminal CRC packet recevied
  Illegal CRC packet request
  Unexpected non-DT Data Phase
scsi2:A:3: Missed busfree. Lastphase = 0xe0, Curphase = 0x0

sdc should be the external RAID array but it is not seed by Linux after 
this message and not usable.

The rest of dmesg is normal, except for this part and the hardware 
configuration didn't change,
only the kernel.

Any comment apreciated,

Thanks,

    Nicolas Bouthors



                 reply	other threads:[~2004-08-02  7:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=410DF47A.1060501@nbi.fr \
    --to=guizmow@nbi.fr \
    --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.