From owner-freebsd-current@FreeBSD.ORG Tue Sep 30 17:42:04 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A9C73EE for ; Tue, 30 Sep 2014 17:42:04 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (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 0BFF9F47 for ; Tue, 30 Sep 2014 17:42:04 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id fb1so8475672pad.39 for ; Tue, 30 Sep 2014 10:42:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=gCfBqSfHd/zJrIYYJXscJV4Y5zIZttvPTqqrAdYi5tc=; b=pFXtUrt/vYQrLMjlp9t5SxX8wjHMBAjCtJX0p9Kyf6KyqaXxAo+13qN0qmDLbz4sj2 WGmYbmR9zSw3E+L50cuD65Ab5MJkq06h5kb767EWxpQ0KGZshC1qEAifkOeIt7eLUxeH 8Z8duyEShspgPof3CtbRy5VwBrOANyOwtUZNgzdn2Z6V7SwPAuhs6BlhCS8wIiyPzaRO NXP3jGoJTvUGLufzrtdgvKF0yZOKQm5PkHDogHg/2TYo+FvanK7SrEEg+t2uH2dW/jXC VgJG5ZqEfXm1bvWvWULFijMK9/nXJlYMo8pbvVcKe0LPb5q2G00taTYiVSnoc/5o1WpJ RDOA== X-Received: by 10.70.95.229 with SMTP id dn5mr20174650pdb.4.1412098923587; Tue, 30 Sep 2014 10:42:03 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id cw5sm15725481pbc.9.2014.09.30.10.42.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 10:42:01 -0700 (PDT) References: <201409281152140359.008FD377@smtp.24cl.home> <201409281153050191.00909A0F@smtp.24cl.home> <4821117AE9E7452FB73D452060B1E4CF@multiplay.co.uk> <201409291603440911.019119CE@smtp.24cl.home> <20140929210142.M26034@beckpeccoz.com> <201409301044110291.0060BD57@smtp.24cl.home> <20140930172522.M83009@beckpeccoz.com> Mime-Version: 1.0 (1.0) In-Reply-To: <20140930172522.M83009@beckpeccoz.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <1BC56699-412E-428C-973B-B86076451362@gmail.com> X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: Looping during boot-up process in FreeBSD-11 current Date: Tue, 30 Sep 2014 10:41:59 -0700 To: =?utf-8?Q?Jos=C3=A9_P=C3=A9rez_Arauzo?= Cc: "Mike." , "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: Tue, 30 Sep 2014 17:42:04 -0000 > On Sep 30, 2014, at 10:31, "Jos=C3=A9 P=C3=A9rez Arauzo" wr= ote: >=20 > Hi Garrett, >=20 > On Tue, 30 Sep 2014 09:57:19 -0700, Garrett Cooper wrote >>> On Sep 30, 2014, at 7:44, "Mike." wrote: >>>=20 >>> On 9/29/2014 at 11:04 PM Jos=C3=A9 P=C3=A9rez Arauzo wrote: >>>=20 >>> |This encoded message has been converted to an attachment. >>> | >>> |Hi Mike, >>> | >>> |On Mon, 29 Sep 2014 16:03:44 -0400, Mike. wrote >>> [...] >>> |So that should put a time bracket on the issue,=20 >>> |roughly the first half of 2014. >>> | >>> |can you boot 271146? Just buildkernel and installkernel. Thank >>> |you. >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> There doesn't seem to be much, if any, interest on the part of the >>> FreeBSD developers in fixing this recently-introduced issue with >>> booting up FreeBSD. =20 >>>=20 >>> Since I experience the problem only on the one notebook of mine, I'll >>> just re-purpose that notebook for OpenBSD and try to find another old >>> notebook that works with FreeBSD. Seems like the path of least >>> resistance for me.... >>=20 >> Did you boot with boot -d, using a stripped down kernel, and without=20 >> SMP like I suggested in another post? >=20 > This suggestion was address to me, not Mike. :) >=20 > I tried, as you suggested, I can reach vfs_mountroot if I don't > include AHCI, so it must be that. >=20 > Now I'm trying to take out SMP and add extra debugging things here and > there. Another suggestion might be to compile the driver as a module or vice versa -= - what happens then? Why this is slightly more interesting sometimes is that compiling drivers in= to the kernel statically allows compilers to optimize out code, which may or= may not positively effect driver runtime (performance and functionality wis= e). It shouldn't affect driver load order though; that should be determinist= ic as long as the drivers and hardware (firmware and configuration) don't ch= ange. > I'm not sure what I'm doing, but I do it anyway. In the worst case I'm > learning something. >=20 > Thank you for your suggestions! NP!=