Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Feb 1997 21:24:39 -0700 (MST)
From:      Nate Williams <nate@mt.sri.com>
To:        Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
Cc:        jfieber@indiana.edu, nate@mt.sri.com, current@freebsd.org, se@freebsd.org
Subject:   Re: new NCR errors in 2.2 branch
Message-ID:  <199702220424.VAA05687@rocky.mt.sri.com>
In-Reply-To: <9702220401.AA28006@cabri.obs-besancon.fr>
References:  <Pine.BSF.3.95q.970221203029.12505A-100000@fallout.campusview.indiana.edu> <9702220401.AA28006@cabri.obs-besancon.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
>  >> I just updated my sources after a 2 week trip, and now I'm getting
>  >> these.
>  >> 
>  >> ncr0 <ncr 53c810 scsi> 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 <ncr 53c810a scsi> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702220424.VAA05687>