From owner-freebsd-isp Mon Aug 24 06:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26092 for freebsd-isp-outgoing; Mon, 24 Aug 1998 06:32:26 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from hack.babel.dk (hack.babel.dk [194.255.106.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26083 for ; Mon, 24 Aug 1998 06:32:23 -0700 (PDT) (envelope-from shredder@hack.babel.dk) Received: from localhost (shredder@localhost) by hack.babel.dk (8.9.0/8.9.0) with SMTP id PAA20395; Mon, 24 Aug 1998 15:31:24 +0200 (CEST) Date: Mon, 24 Aug 1998 15:31:23 +0200 (CEST) From: chrw To: Eddie Fry cc: isp@FreeBSD.ORG Subject: Re: Kernel Error In-Reply-To: <35DF03BE.D13ED143@eaznet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 22 Aug 1998, Eddie Fry wrote: Could be a bug in the driver for the disk controller.The older versions like 2.2.2 had/has a lot of problems with the adaptec controllers. My bet is that you upgrade to newest stable release (pt 2.2.7) and the problem will go away. CW > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message