From: "didier" <didier@ece.gatech.edu>
To: "'Justin T. Gibbs'" <gibbs@scsiguy.com>, linux-scsi@vger.kernel.org
Subject: RE: Pb between an UltraTrak SX8000 and an Adaptec 29160
Date: Mon, 18 Nov 2002 08:01:13 -0500 [thread overview]
Message-ID: <000501c28f02$934b3000$13e2cf82@darkwolf> (raw)
In-Reply-To: <47810000.1037389984@localhost>
The UltraTrak was updated to the latest available firmware
before connected to the server.
I e-mailed promise tech-support last week but did not get
any answer so far.
On a different note, who should I contact regarding the display
bug:
Nov 14 11:04:35 dagdhasrv kernel: (scsi0:A:0): 160.000MB/s transfers
(80.000MHz DT, offset 62, 16bit)
Nov 14 11:04:35 dagdhasrv kernel: SCSI device sda: -1951217920 512-byte
hdwr sectors (100488 MB)
^^^^^^^^^^^
Nov 14 11:04:35 dagdhasrv kernel: Partition check:
Nov 14 11:04:35 dagdhasrv kernel: sda: sda1
Thanks again, Didier.
> > I have just connected a brand new UltraTrak SX8000
> > (from Promise with 8 x 200GB IDE drives) to an
> > adaptec 29160. The UltraTrak SX8000 is connected
> > via a brand new LVD cable (1meter).
> >
> > While everything seems fine, I am getting a bunch of
> >
> > (scsi0:A:0:0): parity error detected in Data-out phase.
> SEQADDR(0x56)
> > SCSIRATE(0xc2)
> > No terminal CRC packet recevied
>
> I've never seen false positives from this diagnostic. It
> looks like your Promise device is not properly implementing
> DT transfers. Is there a firmware update for the device?
next prev parent reply other threads:[~2002-11-18 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 20:50 Pb between an UltraTrak SX8000 and an Adaptec 29160 didier
2002-11-15 19:53 ` Justin T. Gibbs
2002-11-18 13:01 ` didier [this message]
2002-11-18 13:38 ` Alan Cox
2002-11-20 13:53 ` didier
2002-11-20 14:33 ` Alan Cox
2002-11-20 15:22 ` Simon Burley
2002-11-20 15:35 ` Mike Dresser
2002-11-20 16:08 ` Alan Cox
2002-11-18 20:07 ` Andre Hedrick
2002-11-18 23:22 ` Alan Cox
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='000501c28f02$934b3000$13e2cf82@darkwolf' \
--to=didier@ece.gatech.edu \
--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.