From owner-freebsd-current@FreeBSD.ORG Thu Sep 25 21:50:21 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 94AF67C7 for ; Thu, 25 Sep 2014 21:50:21 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 616CA6BE for ; Thu, 25 Sep 2014 21:50:21 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id x19so13964044ier.8 for ; Thu, 25 Sep 2014 14:50:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Ls1QDXMziSycZACRKX13iCppCRFo56iCRaiDcZn+aW0=; b=XVK8IJUs4lGYBDaOYWX/n1eZsVbzy3/NIp9g1rg2bIkRhTY2nHCeWWuP54qspOp77O hXZvB328Z63IjBw0ygS7wBoeKYnbtjdX1t/i3RbguK4sFXwFOfelH1tjWAEksAt/5BiS knitP7h/hb1ubDqeXDVs3yzpMy+MsDUkzJ3k+2axfZBMPIFjRauSjuYduNSyTrZKP2ww 9RsVipZEaSGXAg3/Py0S85oulvpC+LWM094MVipcfNi+sKe3J1s629W3U0JL95eO+pkR kvaLWudarulSNhW/ABdCYGWhht7bZgAi5CPnhLGwos2r0WHfEFnIxMeJzLryS8jkOcUI SjSw== X-Received: by 10.50.138.194 with SMTP id qs2mr8466004igb.4.1411681820754; Thu, 25 Sep 2014 14:50:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.32.143 with HTTP; Thu, 25 Sep 2014 14:50:00 -0700 (PDT) In-Reply-To: <531457FF.3080005@citrix.com> References: <531457FF.3080005@citrix.com> From: Yuriy Taraday Date: Fri, 26 Sep 2014 01:50:00 +0400 Message-ID: Subject: Re: IXP700 AHCI fails to initialize To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-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: Thu, 25 Sep 2014 21:50:21 -0000 On Mon, Mar 3, 2014 at 2:22 PM, Roger Pau Monn=C3=A9 wrote: > On 01/03/14 19:00, 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 pur= ge > > all legacy unrelated configs and other stuff. > > > > The problem I faced is as follows. I have a (rather old) motherboard wi= th > > 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 i= n > > 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 a= nd > > 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 reall= y > > bad and pointers that cabling might be the problem. But I have absolute= ly > > 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. > > This is just a shot in the dark, I'm not familiar with the AHCI driver, > but since you seem to be loosing interrupts (or I would say so based on > the timeout messages), you could try to disable MSI/MSI-X and fallback > to PCI intline IRQs. Could you try to boot with > hw.pci.enable_msix=3D0,hw.pci.enable_msi=3D0? > A flood of RC news in my feed forced me to get back to upgrading my homeserver. I've tried out 10.1-BETA2 image and got the same results. Then I've tried to provide these options you suggested, and although there were some hickup (HDDs didn't respond well at first, I guess), I got to bsdinstall prompt. Thank you very much for suggestion! Now I wonder what would be the impact of having these options disabled permanently. Will there be a huge slowdown of all PCI cards? Or should it be negligible? --=20 Kind regards, Yuriy.