From owner-freebsd-current Mon Jan 21 22:38: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 6E99E37B404 for ; Mon, 21 Jan 2002 22:37:55 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id g0M6bam15911; Tue, 22 Jan 2002 07:37:36 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200201220637.g0M6bam15911@freebsd.dk> Subject: Re: 48bit ATA addressing problems / Promise TX2 ata133 problem? In-Reply-To: To: Mike Brancato Date: Tue, 22 Jan 2002 07:37:36 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Mike Brancato wrote: > I'm running -current and have a Maxtor 160GB hdd hooked to the promise > ata133 card that came with it.... it will flake out for no apparent > reason. any clues? maybe bad hardware? anyone else getting these? > > ad4: READ command timeout tag=0 serv=0 - resetting > ata2: resetting devices .. done > ad4: READ command timeout tag=0 serv=0 - resetting > ata2: resetting devices .. done > ad4: READ command timeout tag=0 serv=0 - resetting > ata2: resetting devices .. done > ad4: READ command timeout tag=0 serv=0 - resetting > ad4: trying fallback to PIO mode > ata2: resetting devices .. done I know that the 48bit code works, but the support code for the Promise ATA133 controller hasn't been tested much (I dont have such an animal). However if you move the disk to another controller, does the problem persist ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message