*BSD News Article 93224


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news-xfer.netaxs.com!europa.clark.net!news.fred.net!usenet
From: Dale Ghent <daleg@maximum.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.2-... random reboots?
Date: Wed, 09 Apr 1997 17:32:56 -0400
Organization: The Secret Organization
Lines: 36
Message-ID: <334C0B08.41C67EA6@maximum.net>
References: <5hfg9m$m3p@news.gvsu.edu> <5hten6$guu@ui-gate.utell.co.uk> <5hu2d7$3br$1@xmission.xmission.com> <5i5l27$p6s@hpg30a.csc.cuhk.edu.hk>
NNTP-Posting-Host: orion.digex.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 4.1.4 sun4m)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38825

> We have the same problem with squid running in 2.1.7.  I am not sure
> whether it's caused by the Adaptec 2940 driver bug anyway.

Maybe this can shed some light... I upgraded my news server (with 3 2940
SCSI controllers) to 2.2.1 from 2.1.5-RELEASE and now and then the
server will reboot itself. I look in /var/log/messages and this is the
error it reports just before it reboots:

Apr  9 16:53:40 news /kernel: sd4(ahc1:6:0): SCB 0x6 - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Apr  9 16:53:40 news /kernel: SEQADDR == 0x8
Apr  9 16:53:40 news /kernel: Ordered Tag queued
Apr  9 16:53:40 news /kernel: sd4(ahc1:6:0): SCB 0x5 timedout while
recovery in progress
Apr  9 16:53:41 news /kernel: sd4(ahc1:6:0): SCB 0x6 - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Apr  9 16:53:41 news /kernel: SEQADDR == 0x6
Apr  9 16:53:41 news /kernel: sd4(ahc1:6:0): Queueing an Abort SCB
Apr  9 16:53:41 news /kernel: sd4(ahc1:6:0): Abort Message Sent
Apr  9 16:53:41 news /kernel: sd4(ahc1:6:0): SCB 6 - Abort Completed.
Apr  9 16:53:41 news /kernel: sd4(ahc1:6:0): no longer in timeout
Apr  9  news /kernel: Ordered Tag sent
Apr  9 16:53:50 news /kernel: sd4(ahc1:6:0): SCB 0x5 - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Apr  9 16:53:50 news /kernel: SEQADDR == 0x5
Apr  9 16:53:50 news /kernel: Ordered Tag queued

And then reboot...

Notice the 9 second delay in the log (16:53:41 - 16:53:50). This always
happens with sd4, which is a Seagate ST51080N. Termination has been
checked. This drive resides on ahc1 (the second controller). This has
happen with both AHC_SCBPAGING_ENABLE turned on and off, and
AHC_TAGENABLE has always been enabled. Any more thoughts on this?

			-Dale G.