From owner-freebsd-stable@FreeBSD.ORG Sat Aug 27 20:32:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15DE716A41F for ; Sat, 27 Aug 2005 20:32:31 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8815443D48 for ; Sat, 27 Aug 2005 20:32:28 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:3861 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.52) id 1E97Lh-0002kL-O6 for freebsd-stable@freebsd.org; Sat, 27 Aug 2005 15:32:22 -0500 Message-ID: <4310CDFD.3070801@goldsword.com> Date: Sat, 27 Aug 2005 16:33:01 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: ICH6 ID'd correctly now, but breaks in 5.4-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2005 20:32:31 -0000 Karl Pielorz wrote: > I recently installed FreeBSD 5.4-R onto my Dell laptop, and it worked > fine. I then updated to 5.4-STABLE (as of 26/08/05) - and it broke... > > Specifically, with the new sources it fails to mount the root files > system - and instead displays: > > " > Mounting root from ufs:/dev/ad0s2a > setrootbyname failed > ffs_mountroot: can't find rootvp > Rout mount failed: 6 > " > > Under 5.4-RELEASE, the IDE controller is ID'd as: > " > atapci0: port > 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 10 at device > 31.2 on pci0 > ... > ad0: 57231MB [116280/16/63] at ata0-master > UDMA33 > " > > Under 5.4-STABLE it's now ID'd as: > " > atapci0: port > 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 17 at device > 31.2 on pci0 > ... > ad0: 57231MB [116280/16/63 > at ata0-master UDMA100 > ad0: FAILURE - READ_DMA status=51 error=4 > LBA=117210177 > ad0: FAILURE - READ_DMA status=51 error=4 LBA=0 > ad0: FAILURE - READ_DMA status=51 error=4 LBA=1 > ad0: FAILURE - READ_DMA status=51 error=4 LBA=0 > ad0: FAILURE - READ_DMA status=51 error=4 LBA=0 > acd0: DVDR at ata1-master PIO4 That's because 5.4 is BROKEN. Check the archives. You will see a lot of us b&t#hing and whining about it. Your original install was operating the controller in generic mode & using PIO and/or DMA33. ANY, repeat ANY attempt to use DMA other than that base mode will cause the errors you are seeing. It's not just the ICH6 chipset. It's not just SATA. It happens with several different chipsets, and with both SATA and PATA. New chipsets and old chipsets. It happens with controllers that used to work & are still marked as working. Since there is NO support for the current ATA driver(1), the only recourse we have been given is to try using Soren's Beta ATA MkIII patches OR jump to a beta release of 6.0. So, I suggest that you try that. Sigh. I've used FreeBSD for my servers since the 2.0.x days. Now I'm trying to get a basic workstation up under the current STABLE release so that I can "give back" by working on my current area of interest (sound subsystem & music creation). Guys, I want to help. But I'm not in a position to devote tons of time to dealing with disk driver issues. My time for this _has_ to be directed to sound and music tools & the underlying components. The sad thing is when we complain and explain why running beta code is not a choice, we get ignored or accused of ranting for the sake of ranting. John (1) Soren has stated publicly that he is not supporting the current code in 5.4. No-one has come forward to try to fix the current mess. ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software