From owner-freebsd-arm@freebsd.org Thu Nov 2 05:28:48 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53460E4FD97 for ; Thu, 2 Nov 2017 05:28:48 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE2C96DD32 for ; Thu, 2 Nov 2017 05:28:47 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id b189so8378329wmd.4 for ; Wed, 01 Nov 2017 22:28:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:reply-to:subject:to:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kRzxsnB91Ikdp12ZvgCRpk/Obnk9csxtPk/dVU5C7UE=; b=pw204yQCzfNDft+6QRtxItZxsN9j9+oUHAqLHCvu4IvVJ/E4yfUu/99g13EpHpJ5QP 3ER+HEwfSw8vqAqg/z4XO1mX/8lchJbJ5kKFu+Ce8I9J+qJPKHGj4jLguSsWxgYpRBM7 ht6r88nAZx4NRRUNjgAP0pF3/XG2RN2IZbHSpC1bxXCeEPQtkVVDSZrJV5PqjHA9F4Lx XWcKWoDg9kbZKZPdzdYcx84wezhwHkmp0Mym22FNMyQFHsdiiOVT32sd8Mk4Lzzfg3mR Ho4b/tBFQSGg1TnPK0XncJLM8rL37TwomefBLZPZGdhYrlMlWaeeC3PN9DadataCXuFh ZbeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:reply-to:subject:to:references:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kRzxsnB91Ikdp12ZvgCRpk/Obnk9csxtPk/dVU5C7UE=; b=OPdEAnhfNNBvIArPe8HnQ3Y/PMfH45dxps9yWYMBGNvseVRY0wnbansIJN9BC7hYw6 mtaocAHtPxrtNpkB3apcUiJWX6mLJdBmbFRmivu3XjYeHpguDw0B7g+7bbidmVY25zoo taiWsGpQUsM4O0os4Fl5RZv5hOP/UuwBLHGe/2qlVmxBrw1gRwEA1NfI9dT7myrgz4G6 JFqe6j5gSi0gDcjNF9OIDQBWeiubls9zfoNSd1VX+zCBpssYDwRmi102pRqlpflU/gWK IXG6Ol4vJ4QONZRW+OLOCy0YAj2y2f7M0IdZ9ruZriwYeOtnaC+zjU3MOm+ixdygQD3a OmWQ== X-Gm-Message-State: AMCzsaVCWqBdmLfB2qNlA1D/BQJmGizKV02lPw0WWRl0WbgnWyE51qJk LHjLqw5oQ6/Sztuj0PqEkEIns+Zt X-Google-Smtp-Source: ABhQp+RJoPwkIGkItw7rMbK7g5C+L+eUSk6hlePc9/RP+BmkVTZB4xPBR8gmPzppTHMA0S5YClLUqw== X-Received: by 10.28.154.137 with SMTP id c131mr564841wme.142.1509600525248; Wed, 01 Nov 2017 22:28:45 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id l96sm3463427wrc.21.2017.11.01.22.28.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 22:28:44 -0700 (PDT) From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: meloun.michal@gmail.com Subject: Re: RPi2 snapshot for armv7 won't boot. To: freebsd-arm@freebsd.org References: <86fu9xmx3u.fsf@elm.localnet> <5B61C831-45A1-454F-B38B-DCE40B969F95@dsl-only.net> Message-ID: Date: Thu, 2 Nov 2017 06:28:53 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2017 05:28:48 -0000 On 02.11.2017 2:53, Kyle Evans wrote: > On Nov 1, 2017 6:24 PM, "Mark Millard" wrote: > > On 2017-Nov-1, at 3:51 PM, Carl Johnson wrote: > >> I had previously tried to upgrade my RPi2 12.0-CURRENT system from armv6 >> to armv7, but it then refused to boot. This time I downloaded the >> latest snapshot (r325156 from 20171030) and it also refuses to boot for >> exactly the same reason. In every case the kernel loads, but then it >> reports that init has died, and then panics and drops into kdb. It >> gives a stack backtrace, but that doesn't mean anything to me. >> >> Is this just me, or is anybody else having this problem? If others have >> the problem, is there some workaround to get it working? >> >> Thanks in advance for any ideas. > > Others are also seeing the problem, not just on > RPI2's. > > It looks like it broke between: > > -r324743 and -r325156 > > someplace relative to whatever is causing the > init problem. > > Details that lead me to that conclusion, if > you care. . . > The r324938 breaks all statically linked binaries (init, /rescue/*, ...). I have prepared patch, but I need a day or two for more testing on other arches. https://github.com/strejda/tegra/commit/67ea3325c50770b5031ef02882b2dccdd1f7611f Michal > One of the FreeBSD folks contacted me privately because his > bananapi-m3 experiments were getting the init problem and > he was hoping I could test independently to see if the > problem was local to his attempt to modernize the BPI-M3 > support so it would again eventually be supported. > > I had to be doing other things but was able to report > that my context was a working variant of -r324743 and > showed him the two small diffs that I used. (The issues > needing the diffs are not tied to any init behavior.) > > He tried his experiment against -r324743 and his > experimental code and *.dt* based .dts booted fine. > > It looks like something after -r324743 broke things > such that the init problem exists for armv7. > > [I'm still not active for investigating any of this.] > > === > Mark Millard > markmi at dsl-only.net > > > For any interested: I think I've got it narrowed down to somewhere between > or including r324950 - r324882 (last good I've tested). > > Looking at the logs, I don't see too many commits in there that could've > broken something this fundamental, but I think my bisect only has three > more steps until I can say for sure. > > Thanks, > > Kyle Evans > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >