From owner-freebsd-scsi Sat Jan 6 21:35:32 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 6176737B400 for ; Sat, 6 Jan 2001 21:35:13 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f075Xgg74385; Sun, 7 Jan 2001 01:33:42 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 7 Jan 2001 01:33:42 -0400 (AST) From: The Hermit Hacker To: "Kenneth D. Merry" Cc: Subject: Re: parity error detected in ... In-Reply-To: <20010106222421.A36036@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org will do, thanks ... On Sat, 6 Jan 2001, Kenneth D. Merry wrote: > On Sat, Jan 06, 2001 at 14:44:54 -0400, The Hermit Hacker wrote: > > > > newest 4.2-STABLE kernel, two scsi bus, 3 drives each ... and i'm getting > > the following: > > > > Jan 6 14:27:54 poseidon /kernel: ahc0:A:0: parity error detected in Message-in phase. SEQADDR(0x121) SCSIRATE(0x0) > > Jan 6 14:27:54 poseidon /kernel: ahc0:A:0: parity error detected in Message-in phase. SEQADDR(0x121) SCSIRATE(0x0) > > That looks like a cabling/connector problem of some sort. > > I would suggest checking your cabling and termination. > > > Jan 6 14:28:09 poseidon /kernel: (ahc0:A:0:0): refuses tagged commands. Performing non-tagged I/O > > Jan 6 14:28:09 poseidon /kernel: (ahc0:A:0:0): refuses tagged commands. Performing non-tagged I/O > > Jan 6 14:28:09 poseidon /kernel: ahc0:A:0: Target did not send an IDENTIFY message. LASTPHASE = 0x0, SAVED_SCSIID == 0x7 > > Jan 6 14:28:09 poseidon /kernel: ahc0:A:0: Target did not send an IDENTIFY message. LASTPHASE = 0x0, SAVED_SCSIID == 0x7 > > Jan 6 14:28:09 poseidon /kernel: ahc0: Issued Channel A Bus Reset. 64 SCBs aborted > > Jan 6 14:28:09 poseidon /kernel: ahc0: Issued Channel A Bus Reset. 64 SCBs aborted > > From the timestamps, those may just be generic problems caused by the parity > errors. > > So try looking at cabling and termination and see if that helps things. > > Ken > -- > Kenneth Merry > ken@kdm.org > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message