From owner-freebsd-current Wed Dec 23 04:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08670 for freebsd-current-outgoing; Wed, 23 Dec 1998 04:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08651 for ; Wed, 23 Dec 1998 04:25:57 -0800 (PST) (envelope-from starr3@gccs.com.au) Received: from lb50x (lb50x.gccs.com.au [203.17.152.10]) by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id WAA02640; Wed, 23 Dec 1998 22:25:33 +1000 (EST) Message-ID: <002f01be2e6f$56a16d60$0a9811cb@gccs.com.au> From: "Harry Starr" To: , "current" Subject: Re: Problems with CAM and ncr Date: Wed, 23 Dec 1998 22:25:33 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I did put a "disable tags" quirk into cam_xpt.c, and it seems to be stable now. Is/Has anyone had success using the CAM stuff against IBM Ultrastar drives (9GB, 18GB) ?? I plan on switching to those when I retire these "old", problematic CONNERs. Harry. ----- Original Message ----- From: Geoff Buckingham To: Harry Starr ; current Sent: Wednesday, December 23, 1998 9:21 PM Subject: Re: Problems with CAM and ncr >On Tue, Dec 22, 1998 at 10:45:38PM +1000, Harry Starr wrote: >> There seems to be a major problem with the new CAM code and the ncr driver. >> >> Config: >> >> Asus SC200 (ncr810) in Asus P2L97 M/B with PII-300 and 128MB mem. >> >> With "hard" disk access (Make world; or Make release), more than likely, the >> ncr driver will give an error message of ncr:::queue empty, at which point >> the system will lock up (pager errors, etc). This is almost 100% >> reproducible. >> >> The SCSI drives are "old" Conner Cp3470. I'm not sure if there were problems >> with tagged queueing in this model; but they worked OK in a DG/UX system. >> >Someone more knowledgable than me will doubtless be along in a bit, but >I have had the NCR driver working with CAM for build world etc without >problems however that machine has a 'modern' drive. > >You may be able to eliminate TAG problems by adding a quirk to >/usr/src/sys/cam/cam_xpt.c specifying a lower maxtags, then compiling >a new kernel. I have one for a hardware RAID which was causing hangs: > > { > /* Delf Stuff */ > { > T_ANY, SIP_MEDIA_REMOVABLE|SIP_MEDIA_FIXED, > /*vendor*/"C_Design", /*product*/"DELFRaid", /*revision*/"0131 >" > }, > /*quirks*/0, /*mintags*/24, /*maxtags*/28 > }, > >This seems to have fixed it (one week uptime, was crashing within 30 mins of >disk load) > >If someone from the CAM group happens along: Is there a methed for submision >and review of such quirks? I have raised a non critical kernel PR for the >above, although I must revise it as I have altered min/maxtags since >submiting it. > >There is no scientific method for the values chosen above, they just >seem to prevent the hangs and excesivly uneven distribution of TAGs >between logical devices within the RAID. > >> The ncr driver previously reports that "tagged openings is now 31". >> >> Reverting to a kernel dated "8-Aug-1998" alleviates the problem. >> >> Any thoughts ?? >> >-- >GeoffB > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message