From owner-freebsd-current@FreeBSD.ORG Fri Jul 9 15:26:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB68716A4CE; Fri, 9 Jul 2004 15:26:13 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id A21CB43D3F; Fri, 9 Jul 2004 15:26:12 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i69FQ8Xa013375 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 17:26:08 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i69FQ8NA013374; Fri, 9 Jul 2004 17:26:08 +0200 (CEST) Date: Fri, 9 Jul 2004 17:26:08 +0200 From: Divacky Roman To: current@freebsd.org Message-ID: <20040709152608.GA13255@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: sos@freebsd.org Subject: via 8237 and above-udma33 problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 15:26:14 -0000 Hi I've got via 8237 ata driver with a new big seagate (ST3160023A) disk.. If transfer mode is set above udma33 (ie. to udma100 which is default) I'm getting on writing these errors: ad2: 152627MB [310101/16/63] at ata1-master UDMA100 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2208287 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2208287 ad2: FAILURE - WRITE_DMA status=51 error=84 LBA=2208287 it seems this is printed out after each ata transfer (ie. its repeating). after several (hundred?) iterations it hangs in kernel panic I have two questions 1) is there any solution for this driver not hanging on udma>33 ? 2) if not - how may I tell fbsd to initialize this drive (resp. the channel the drive is attached to) to udma33 instead of the default mode. I want to boot from that drive so I cannot use atacontrol or whatever since it would have hanged before I'd enter user-space system initialization thnx for reponse! roman P.S. I can provide more info, just ask for it. and I also might experiment with that drive.