From owner-freebsd-hackers Wed Dec 15 15:56:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3FFAB15625 for ; Wed, 15 Dec 1999 15:56:15 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA08720; Wed, 15 Dec 1999 16:55:51 -0700 (MST) (envelope-from ken) Date: Wed, 15 Dec 1999 16:55:51 -0700 From: "Kenneth D. Merry" To: WHS Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout Message-ID: <19991215165550.A8672@panzer.kdm.org> References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3858372B.D5BBFAF@xs4all.nl>; from whs@xs4all.nl on Thu, Dec 16, 1999 at 12:49:47AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 00:49:47 +0000, WHS wrote: > Thomas David Rivers wrote: > > > > > > > > The kernel hangs (rather an endless loop) with messages like: > > > > > > ncr0: timeout nccb=0xc0c38000 > > > > > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the > > > ncr source it seems there's a problem with the script stuff in case of a > > > timeout. Anyway, this doesn't happen with either the obsd or linux ncr > > > driver (both derived from the fbsd one I believe), so that may provide > > > some info for whoever maintains this driver. > > > > > > Please mail me with suggestions or pacthes to try out as I need the MO > > > drive. > > > > > > Regards, > > > > > > Wouter > > > > You didn't say which version of FreeBSD you're using.... > > Oops.. It's 3.3 (RELEASE I guess, the oct cdrom). Depending on what sort of NCR board you have, I would suggest trying out the new sym driver, written by Gerard Roudier . It is located here: ftp://ftp.tux.org/tux/roudier/drivers/freebsd/experimental/ Look at the readme file in that directory to determine whether your board is supported. If you have questions, problems, etc., with the sym driver, contact Gerard. In general, the stock NCR driver isn't being actively maintained, and your problem could be the result of a bug in the driver, or some problem with your MO drive. It's hard to say for sure. Gerard's driver is actively maintained, though, so if you still have problems with his driver, it'll be easier to get the problems fixed. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message