From owner-freebsd-isp Sat Aug 22 10:41:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22356 for freebsd-isp-outgoing; Sat, 22 Aug 1998 10:41:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from amber.eaznet.com ([216.19.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22345 for ; Sat, 22 Aug 1998 10:41:53 -0700 (PDT) (envelope-from eddie@eaznet.com) Received: from eaznet.com (admin.eaznet.com [216.19.20.16]) by amber.eaznet.com (8.8.7/8.8.5) with ESMTP id KAA00914 for ; Sat, 22 Aug 1998 10:42:19 -0700 (MST) Message-ID: <35DF03BE.D13ED143@eaznet.com> Date: Sat, 22 Aug 1998 10:45:35 -0700 From: Eddie Fry X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: isp@FreeBSD.ORG Subject: Kernel Error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running 2.2.2 and have just recently started having my machine lockup with: Aug 22 03:00:00 amber /kernel: sd1(ahc0:6:0): UNIT ATTENTION asc:29,0 Aug 22 03:00:00 amber /kernel: sd1(ahc0:6:0): Power on, reset, or bus device reset occurred Aug 22 03:00:00 amber /kernel: , retries:4 Aug 22 03:19:14 amber /kernel: Unexpected busfree. LASTPHASE == 0x0 Aug 22 03:00:00 amber /kernel: SEQADDR == 0x12b Then the machine locks up. Do these errors indicate a drive problem or a controller problem? Any Ideas??? Eddie -- Eddie Fry EAZNet Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message