From owner-freebsd-current@FreeBSD.ORG Mon Mar 3 10:59:50 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D02D5915 for ; Mon, 3 Mar 2014 10:59:50 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AA7E7818 for ; Mon, 3 Mar 2014 10:59:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=9IXDpUN1VW3lJi5quecNXLjcWBBvySdYIOPcMZoDzYI=; b=V1ZU+ACYGzm/x75AAgQK3Wau3sefmNJa8wMULRpj0S8TTRGq+Wx/NloUGo50cx6p1+M/T0/NLUgaUEkOcV8BSxWYCLkTecnojgPyfGoMqNr5tZ46+8yzoR6LQoHifgpdW5GBHgvoETT+Pk4be9kygHXHVh3Bj585SEuijEPae1w=; Received: from [182.3.161.159] (port=44796 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WKQb1-000Gtq-6f; Mon, 03 Mar 2014 03:59:44 -0700 Date: Mon, 3 Mar 2014 18:59:38 +0800 From: Erich Dollansky To: Yuriy Taraday Subject: Re: IXP700 AHCI fails to initialize Message-ID: <20140303185938.0b5ab540@X220.alogt.com> In-Reply-To: References: X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Mon, 03 Mar 2014 10:59:51 -0000 Hi, ok, I do not know of a working solution. But something like this happened to me too. I simply could not get newer FreeBSD versions working on old hardware. I have had to stick then with 7 until a lightning put an end to the affected machine. You still have one other chance. Try 9. My strategy in upgrading is also very simple. When I get a new machine, I install CURRENT and stick with the branch it will become later until this branch is not supported anymore. It saved me a lot of hassles as I normally have to do just one big version jump if the machine gets real old I have have to switch version. Erich On Sat, 1 Mar 2014 22:00:52 +0400 Yuriy Taraday wrote: > Hello. > > I currently have FreeBSD 8.3 on my home server and it works fine but > it's time to upgrade at last (new ath and new ipfw especially allure > me). I've decided to go straight to 10.0 and reinstall system from > scratch to purge all legacy unrelated configs and other stuff. > > The problem I faced is as follows. I have a (rather old) motherboard > with integrated SATA controller that presents in the OS as IXP700. In > 8.3 it works fine. I have 2 disks attached to it: one with all my > data and another one destined to be new system disk. I also have one > IDE disk installed that is currently used as system disk. > > When I booted from USB stick with 10.0, I couldn't see any SATA disks > in the system. I dug into dmesg and found this: > http://pastebin.com/wv2A0MUE As it seems AHCI controller or disks are > not responding to commands and timeouts eventually. > > A friend suggested to try CURRENT image. I went > with FreeBSD-11.0-CURRENT-amd64-VT-20140222-r262336-mini-memstick.img > and got almost the same error: http://pastebin.com/0iGaSWUD > The error repeats and never stops (looks like CURRENT images have > different config) but it is essentially the same. > > I've googled the problem but found only notes about how IXP700 is > really bad and pointers that cabling might be the problem. But I have > absolutely no problems with 8.3, so it looks like some regression > during further development (shift to CAM, maybe?). > > Please help me to identify and fix the problem. >