From owner-freebsd-scsi  Tue Dec 14 13:40:14 1999
Delivered-To: freebsd-scsi@freebsd.org
Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 24E81150E2; Tue, 14 Dec 1999 13:40:11 -0800 (PST)
	(envelope-from mreimer@vpop.net)
Received: from vpop.net (bilbo.vpop.net [216.160.82.65])
	by boromir.vpop.net (8.9.1/8.9.1) with ESMTP id NAA25151;
	Tue, 14 Dec 1999 13:40:10 -0800 (PST)
Message-ID: <3856B93D.4D962CB1@vpop.net>
Date: Tue, 14 Dec 1999 13:40:13 -0800
From: Matthew Reimer <mreimer@vpop.net>
Organization: VPOP Technologies, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RC i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-scsi@FreeBSD.ORG
Subject: Re: Unexpected bus free & swap_pager: indefinite wait buffer
References: <199912142011.MAA00665@mass.cdrom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mike Smith wrote:
> 
> > We're running 3.3-stable from about 10/21/1999 on a machine that we
> > haven't physically touched for about four months. It has a (supposedly
> > good) LVD cable with a terminator at the end of the cable, that came
> > with the Asus motherboard. Last night, the kernel started printing the
> > errors below and the machine became unusable: couldn't login,
> > unresponsive shells, though it did still respond to pings.
> >
> > The blknos reported in the swap_pager message repeated in a cycle (e.g.,
> > 8944, 328, 8944, 328...), and every now and then another blkno would be
> > added to the cycle, until at the end (just before we hit the reset
> > button) the cycle was
> > 8944,328,2640,174968,44560,42848,40720,3208,512,3160.
> >
> > Are we losing a disk, or is it some kind of bug, or...?
> >
> > Thanks in advance for any help you can offer.
> >
> > Matt
> >
> > Dec 13 17:35:00 merry /kernel: Unexpected busfree.  LASTPHASE == 0x40
> 
> This is indicative of a disk going away, either from a firmware bug or
> overheating.  Everything goes downhill from there (the command has been
> lost, and we don't recover well from that).

Thanks for the answer, Mike. The possibility of the disk overheating
fits the symptom of the Adaptec probe taking a long time for that drive.
:(

Matt


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