From owner-freebsd-bugs Sat Jul 11 21:20:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28754 for freebsd-bugs-outgoing; Sat, 11 Jul 1998 21:20:16 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28749 for ; Sat, 11 Jul 1998 21:20:15 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id VAA15990; Sat, 11 Jul 1998 21:20:00 -0700 (PDT) Date: Sat, 11 Jul 1998 21:20:00 -0700 (PDT) Message-Id: <199807120420.VAA15990@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Matthias Buelow Subject: Re: kern/7237: [patch] NCR SCSI driver ch0 troubles Reply-To: Matthias Buelow Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/7237; it has been noted by GNATS. From: Matthias Buelow To: freebsd-gnats-submit@freebsd.org, mkb@mayn.de Cc: Subject: Re: kern/7237: [patch] NCR SCSI driver ch0 troubles Date: Sun, 12 Jul 1998 02:11:59 +0200 Hans Huebner has pointed me out, that there is a SCSI_DATA_IN missing when calling scsi_scsi_cmd in ch.c:ch_getelemstatus. This only seems to affect the NCR controller. I changed it and it seems to work fine. Here's a patch for that particular problem on 2.2-STABLE: --- scsi/ch.c Sun Jul 12 02:08:15 1998 +++ scsi/ch.c.NEW Sun Jul 12 02:08:08 1998 @@ -603,7 +603,8 @@ * Send command to changer. */ return (scsi_scsi_cmd(sc->sc_link, (struct scsi_generic *)&cmd, - sizeof(cmd), (u_char *)data, datalen, CHRETRIES, 100000, NULL, 0)); + sizeof(cmd), (u_char *)data, datalen, CHRETRIES, 100000, NULL, + SCSI_DATA_IN)); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message