From owner-freebsd-current Fri Feb 21 20:25:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA19324 for current-outgoing; Fri, 21 Feb 1997 20:25:09 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19309; Fri, 21 Feb 1997 20:24:47 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id VAA05687; Fri, 21 Feb 1997 21:24:39 -0700 (MST) Date: Fri, 21 Feb 1997 21:24:39 -0700 (MST) Message-Id: <199702220424.VAA05687@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jean-Marc Zucconi Cc: jfieber@indiana.edu, nate@mt.sri.com, current@freebsd.org, se@freebsd.org Subject: Re: new NCR errors in 2.2 branch In-Reply-To: <9702220401.AA28006@cabri.obs-besancon.fr> References: <9702220401.AA28006@cabri.obs-besancon.fr> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> I just updated my sources after a 2 week trip, and now I'm getting > >> these. > >> > >> ncr0 rev 2 int a irq 11 on pci0:12 > >> (ncr0:0:0): extraneous data discarded. > >> (ncr0:0:0): COMMAND FAILED (9 80) @f2111a9c. > >> (ncr0:0:0): "FUJITSU M1606S-512 6220" type 0 fixed SCSI 2 > >> sd0(ncr0:0:0): Direct-Access > >> sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) > >> 1041MB (2131992 512 byte sectors) > >> .... > >> sd0(ncr0:0:0): extraneous data discarded. > >> sd0(ncr0:0:0): extraneous data discarded. > >> sd0(ncr0:0:0): extraneous data discarded. > > > My, that looks familiar! > > > ncr0 rev 17 int a irq 11 on pci0:12 > > ncr0 waiting for scsi devices to settle > > (ncr0:0:0): "FUJITSU M1606S-512 6226" type 0 fixed SCSI 2 > > sd0(ncr0:0:0): Direct-Access > > sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) > > 1041MB (2131992 512 byte sectors) > > ... > > sd0(ncr0:0:0): extraneous data discarded. > > sd0(ncr0:0:0): extraneous data discarded. > > ... > > > With RELENG_2_2 from about a month ago, I discovered that by > > adding: > > > cpu "I486_CPU" > > > to my kernel config (I have a pentium and had removed the line), > > the messages went away. However, I just built a new kernel a > > couple days ago and the messages are back. :( > > This is not related to the presence of this option. You're right. And, as I said I didn't start seeing these until recently. Even the 2.2 sources from 2 weeks ago didn't have them, and neither does 2.1.5, nor a really old version of -current from last July. It's definitely a new error. > I always had it > and I also get the same error (same drive, same controller). I already > noticed this when I installed the disk (~1 year ago). Because I only > get the message with this drive I suppose that this is specific to the > Fujitsu 1606. Maybe, but I doubt it. I'm going to try my old kernel and see if it makes any difference. Nate