Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!PHOENIX.PRINCETON.EDU!perry
From: perry@PHOENIX.PRINCETON.EDU ("Kevin R. Perry")
Newsgroups: comp.sys.sgi
Subject: Re:  kernel and tar errors
Message-ID: <8806161427.AA11892@phoenix.Princeton.EDU>
Date: 16 Jun 88 14:27:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34

>From info-iris-request@brl-vmb.arpa Thu Jun 16 10:03:04 1988
>Date:     Wed, 15 Jun 88 9:40:43 PDT
>From: Fletcher Robinson <frobinso@cirm.northrop.com>
>To: info-iris@BRL.ARPA
>Subject:  kernel and tar errors
>Message-Id:  <8806151244.aa15986@SMOKE.BRL.ARPA>
>
>I have come up against two problems on our new 4D 70G. One machine with
>very little user activity(..waiting for software..), after sitting idle
>for several days will begin to display the following error :
>   error in kernel #42 severity=2 , etc.

Haven't seen this one, sorry.

>
>Another problem is using tar to backup files. There is a profusion of
>the following error message:
>   1ps0d0s6: error csr=0x4000 bn=?????? statcode=83 recovered, errcode=0x1
>accompanied sparingly by :
>   tp7: (18) correctable data error
	
We have experienced this problem on our 4D's.
I recently asked an SGI field service person about it.
He claims the problem is known to SGI, and they're working on it.
It's in the hardware, and they supposedly understand what is wrong.
Something about impedence-matching on something in the
tape-drive unit.  He says it's perfectly safe to ignore these messages,
and maybe someday they'll have a fix.  Hey, at least it gives you
something to watch while you're doing backups! :-)

K.Perry
perry%phoenix@princeton.edu
Sys Prog
Computing & Info. Technology
Princeton Univ.