From owner-freebsd-hardware  Wed Jun 16 15: 9:16 1999
Delivered-To: freebsd-hardware@freebsd.org
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7D67614CB5
	for <hardware@FreeBSD.ORG>; Wed, 16 Jun 1999 15:09:06 -0700 (PDT)
	(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.9.3/8.8.5) id QAA83643;
          Wed, 16 Jun 1999 16:08:59 -0600 (MDT)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199906162208.QAA83643@panzer.plutotech.com>
Subject: Re: What does it mean?
In-Reply-To: <199906150937.NAA21818@shuttle.svib.ru> from Alex Povolotsky at "Jun 15, 1999 01:37:41 pm"
To: tarkhil@asteroid.svib.ru
Date: Wed, 16 Jun 1999 16:08:59 -0600 (MDT)
Cc: hardware@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Alex Povolotsky wrote...
> Hello!
> 
> Just seen the following:
> 
> a-In phase.  Tag == 0x4.
> Jun 15 13:32:26 asteroid /kernel: (da1:ahc0:0:3:0): Have seen Data Phase. 
> Length = 8192.  NumSGs = 2.
> Jun 15 13:32:26 asteroid /kernel: sg[0] - Addr 0x642b000 : Length 4096
> Jun 15 13:33:03 asteroid /kernel: swap_pager: indefinite wait buffer:
> device: 0x20409, blkno: 1648, size: 4096
> Jun 15 13:33:23 asteroid /kernel: swap_pager: indefinite wait buffer:
> device: 0x20409, blkno: 1648, size: 4096
> Jun 15 13:33:26 asteroid /kernel: (da1:ahc0:0:3:0): SCB 0x4 - timed out
> while idle, LASTPHASE == 0x1, SEQADDR == 0xa
> Jun 15 13:33:26 asteroid /kernel: (da1:ahc0:0:3:0): Queuing a BDR SCB
> Jun 15 13:33:26 asteroid /kernel: (da1:ahc0:0:3:0): Bus Device Reset Message
> Sent
> Jun 15 13:33:26 asteroid /kernel: (da1:ahc0:0:3:0): no longer in timeout,
> status = 352
> Jun 15 13:33:26 asteroid /kernel: ahc0: Bus Device Reset on A:3. 1 SCBs
> aborted
> 
> 
> What does it mean? Disks overheating? Or dying? Or something else?

Hard to say what's wrong, although it might help to send the above errors,
and the full dmesg output from the machine, to the freebsd-scsi list.

It also looks like you haven't included all of the errors.  The top line
from your log above is just a partial error message.

There are any number of things that could be wrong, but the most common
problems are cabling or termination problems and drive firmware bugs.

Ken
-- 
Kenneth Merry
ken@plutotech.com


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