Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Mar 1999 16:20:02 -0800 (PST)
From:      "Kenneth D. Merry" <ken@plutotech.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/10332: System freezes during certain SCSI activity
Message-ID:  <199903020020.QAA11438@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/10332; it has been noted by GNATS.

From: "Kenneth D. Merry" <ken@plutotech.com>
To: tege@matematik.su.se (Torbjorn Granlund)
Cc: FreeBSD-gnats-submit@FreeBSD.ORG, gibbs@FreeBSD.ORG
Subject: Re: kern/10332: System freezes during certain SCSI activity
Date: Mon, 1 Mar 1999 17:15:37 -0700 (MST)

 Torbjorn Granlund wrote...
 > 
 > >Number:         10332
 > >Category:       kern
 > >Synopsis:       System freezes during certain SCSI activity
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Mon Mar  1 11:00:01 PST 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Torbjorn Granlund
 > >Release:        FreeBSD 3.1-RELEASE i386
 > >Organization:
 > Swox AB
 > >Environment:
 > 
 > motherboard:	ASUS P2B-S (PCB rev 1.02, BIOS rev 1008)
 > cpu:		Intel Pentium II 400MHz
 > memory:		256MB SDRAM w ECC (2x128MB Samsung GH)
 > disk:		9.1GB U2W Seagate Cheetah (da0, SCSI id 0)
 > disk:		9.1GB U2W Seagate Cheetah (da1, SCSI id 1)
 > disk:		9.1GB U2W Seagate Cheetah (da2, SCSI id 2)
 > disk:		18.2GB U2W Seagate Barracuda (da3, SCSI id 3)
 > tape:		12GB/24GB DDS-1/2/3 FSCSI Sony SDT-9000 (SCSI id 6)
 > scsi:		AHA7890 on motherboard
 > video:		S3 Trio64
 > network:	Intel Etherexpress Pro 100B
 > 
 > >Description:
 > 
 > When accessing the tape drive using the `dump' command, the system hangs
 > within a few hours.  The console then has messages like this:
 > 
 > (da0:ahc0:0:0:0) SCB 0xd - times out in dataout phase, SEQADDR == 0x5d
 > (da0:ahc0:0:0:0) SCB 0x5d - times out in dataout phase, SEQADDR == 0x5d
 > (da0:ahc0:0:0:0) SCB 0x13 - times out in dataout phase, SEQADDR == 0x5d
 >   .
 >   .
 >   .
 > 
 > The system then responds to keyboard input but any disk activity seems to be
 > blocked.  We have waited several minutes but the system remains locked.
 > Occasionally, more messages like the ones above are printed.  The disk
 > mentioned in the messages are sometimes da1 or da2.
 > 
 > The SCSI buses are properly terminated.
 > 
 > We cannot seem to provoke the problem unless the tape drive is accessed.
 > 
 > (We tried to connect a 2nd SCSI controller [an ASUS SC200/Symbios] to a PCI
 > slot, but then the system hangs during boot.)
 
 This sounds like a cabling problem.  The 'timed out in dataout' phase means
 that the SCSI bus was in the data out phase when the 60-second I/O timeout
 hit.  This generally means you have a cabling problem.  (because a signal
 is stuck somewhere and the data transfer didn't complete)
 
 You should check for bent pins on the cable, make sure the cables don't
 run too close to the power supply, and make sure you're using the right
 type of cable, especially for the LVD portion of the bus.  The LVD cable
 should be one of the "twisty" cables with the terminator block at the end.
 
 That is assuming, of course, you're running at LVD speeds.  No matter what
 speed the LVD drives run at, they'll need external termination, because
 they don't have onboard terminators.
 
 Ken
 -- 
 Kenneth Merry
 ken@plutotech.com
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




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