From nobody  Fri Sep 18 21:12:11 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA13530;
          Fri, 18 Sep 1998 21:12:11 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199809190412.VAA13530@hub.freebsd.org>
Date: Fri, 18 Sep 1998 21:12:11 -0700 (PDT)
From: arussell@hos.net
To: freebsd-gnats-submit@freebsd.org
Subject: destructive install of 2.2.7 on 2.2.5 system has scsi proglems
X-Send-Pr-Version: www-1.0

>Number:         7984
>Category:       i386
>Synopsis:       destructive install of 2.2.7 on 2.2.5 system has scsi proglems
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 18 21:20:01 PDT 1998
>Closed-Date:    Mon Mar 29 16:17:36 PST 1999
>Last-Modified:  Mon Mar 29 16:18:33 PST 1999
>Originator:     A.G. Russell
>Release:        2.2.7
>Organization:
>Environment:
FreeBSD bifrost.hos.net 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Wed Jul 22 08:48:29 GMT 1998     root@builder.cdrom.com:/usr/src/sys/compile/GENERIC  i386
>Description:
under load happens very fast, and
Idle takes much longer to see the following:

ncr0:0: ERROR (81:0) (0-a7-80) (8/13) @ (mem 4bc124:00000000).
ncr0: regdump: da 10 c0 13 47 08 00 1f 80 00 80 a7 80 00 07 00.
ncr0: restart (fatal error).
sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0ad0800.
ncr0: timeout ccb=f0ad0800 (skip)

ncr0:0: ERROR (81:0) (8-28-0) (8/13) @ (mem 8bd818:00000000).
ncr0: regdump: da 10 c0 13 47 08 00 1f 00 08 80 28 80 00 00 00.
ncr0: restart (fatal error).
sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0ad0800.
ncr0: timeout ccb=f0ad0800 (skip)


ncr0: timeout ccb=f06be400 (skip)

I first thought this was a termination problem, because I 
purchased a new disk to install on.
But I then replaced the 2.2.5 disk and ran for days with
no problems, under all kinds of loads...

I then installed 2.2.7 on the working 2.2.5 disk and 
wamb bang thank you... there it was.  Same hardware that worked
now shows scsi problems.
>How-To-Repeat:
install 2.2.7, run.
pci-sc200 scsi card
fujitsu 1gig
k6-2 300mhz with 128meg of mem
ne2000 pci
>Fix:

>Release-Note:
>Audit-Trail:

From: "A.G. Russell IV"      <arussell@bifrost.hos.net>
To: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Cc:  Subject: Re: i386/7984: destructive install of 2.2.7 on 2.2.5 system has scsi problems
Date: Mon, 21 Sep 1998 09:43:44 -0500 (CDT)

 "FreeBSD-gnats-submit@FreeBSD.ORG wrote ..."
 > Thank you very much for your problem report.
 > It has the internal identification `i386/7984'.
 > The individual assigned to look at your
 > report is: freebsd-bugs. 
 > 
 > >Category:       i386
 > >Responsible:    freebsd-bugs
 > >Synopsis:       destructive install of 2.2.7 on 2.2.5 system has scsi proglems
 > >Arrival-Date:   Fri Sep 18 21:20:01 PDT 1998
 
 I can turn on any tracing that would be helpful, The system will often stay up long
 enough to build a kernel.
 
 To recap, I see the following, and I have experimented with several drives, and
 methods of termination.  I have not tried an adaptec card yet, but will when
 I can get my hands on one.
 
 
 ncr0:0: ERROR (81:0) (0-a7-80) (8/13) @ (mem 4bc124:00000000).
 ncr0: regdump: da 10 c0 13 47 08 00 1f 80 00 80 a7 80 00 07 00.
 ncr0: restart (fatal error).
 sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0ad0800.
 ncr0: timeout ccb=f0ad0800 (skip)
 
 ncr0:0: ERROR (81:0) (8-28-0) (8/13) @ (mem 8bd818:00000000).
 ncr0: regdump: da 10 c0 13 47 08 00 1f 00 08 80 28 80 00 00 00.
 ncr0: restart (fatal error).
 sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0ad0800.
 ncr0: timeout ccb=f0ad0800 (skip)
 
 
 ncr0: timeout ccb=f06be400 (skip)

From: "A.G. Russell IV"      <arussell@bifrost.hos.net>
To: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Cc:  Subject: Re: i386/7984: destructive install of 2.2.7 on 2.2.5 system has scsi proglems
Date: Thu, 24 Sep 1998 13:03:50 -0500 (CDT)

 "FreeBSD-gnats-submit@FreeBSD.ORG wrote ..."
 > Thank you very much for your problem report.
 > It has the internal identification `i386/7984'.
 > The individual assigned to look at your
 > report is: freebsd-bugs. 
 > 
 > >Category:       i386
 > >Responsible:    freebsd-bugs
 > >Synopsis:       destructive install of 2.2.7 on 2.2.5 system has scsi proglems
 > >Arrival-Date:   Fri Sep 18 21:20:01 PDT 1998
 
 Is there any information that I can send to help debug this?
 
 Thanks in advance.
 
 A.G.
 
 _______________________________________________________________________________
 A.G. Russell IV  KC5KFD        High Order Software        e-mail:   ag4@hos.net
 Phone 512-834-1145
           These are my views, on anyone else they would look silly.
        When it absolutely, positively has to be destroyed by tomorrow...
                           United States Marines Corp
 -------------------------------------------------------------------------------
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Mar 29 16:17:36 PST 1999 
State-Changed-Why:  
Active development on 2.2 branch is over. Please resubmit if this 
problem exists with 3.1 or later. Thanks. 
>Unformatted:
