From owner-freebsd-arm@freebsd.org Thu Nov 2 16:38:45 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 41DF5E5E379 for ; Thu, 2 Nov 2017 16:38:45 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 C4C4E76A for ; Thu, 2 Nov 2017 16:38:44 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wr0-x231.google.com with SMTP id u40so107231wrf.10 for ; Thu, 02 Nov 2017 09:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:reply-to:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UxxsP9f2PeFV5vzqIed0NkgH1po3J70tMsrgBfDr1lE=; b=Da9a/2GeB4Ku344oOYJtxS92Rl4qvGl7yQPeDFthQGyMvsO4JjxXR5vywjEfPIMriK VAZDI7FkpYS8WG49KkyiislvfZ6I2WqIFXM4ZZ5xdPB3OVYEGERjUE92g28IF7AkxgWw 569KIdydY1O0NBV54dwKmbnMbwE1ZWxFlBcUREDEbpbVTEvGhu6ZwiZHI7PGCC94DLYS rXt9qahKy/P4C5NcScnsux78WS8CBKI+KA5B84vtOdWPrpozXcwbSVZs/Hwk3ZoqkimQ OHPR9sSBu1XDxexsGlQJRUqSTgBbXlOQ9ZgEdQma8ajAopFBuVHU2yAYa/2H1NJ75PUg hpPQ== 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:cc:references :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=UxxsP9f2PeFV5vzqIed0NkgH1po3J70tMsrgBfDr1lE=; b=OMp6P7mllPd8mRgri7TLeLuF0wV6GX+ifHzn6P7f87s+9Jf3oqftHlIg/1II3OL1CY Qr88jimyUu7SZeyNnw9AtgOzy/WGFRfUgQcix9zB3j/S1tP83YVX9p9vr4q7tOhKNY15 m16pO+2oWTzAAX9rwZxS/0WDk88R7gLk55wPxQzRxaCKCQy7oGYFQyJHc5kqUpMcinem JXF6NSRVywPYRt0aZ2DdIMTIu1D6dgbe8NNauf46CoCWPxEsex900qK9wOKS1icmErXJ wu8DX1TuCOKd7fFC+kUGnmYOITNEgraOdR50S9IN4Qp/bItS8w68T3Zj4cOf7kTTJ6S1 zHdQ== X-Gm-Message-State: AMCzsaVpaOA0fzt2UvIedB7ffl/+drMEheZW4o0oJBRa7BZxMkIf6bQM klA3FHBg5QMXCSjBWyVBy0fOne/W X-Google-Smtp-Source: ABhQp+RzPzZ2Ozkj/odO1v8s402cB1p2L8yQjD1h4hR0+ru7qPv2bHF3QL7Z2UeuSQ8wzB0XqxjdKQ== X-Received: by 10.223.135.90 with SMTP id 26mr3338556wrz.114.1509640722826; Thu, 02 Nov 2017 09:38:42 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id k185sm47054wma.28.2017.11.02.09.38.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Nov 2017 09:38:42 -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: Warner Losh Cc: "freebsd-arm@freebsd.org" References: <86fu9xmx3u.fsf@elm.localnet> <5B61C831-45A1-454F-B38B-DCE40B969F95@dsl-only.net> Message-ID: <053e80cf-813b-97bd-4890-a954669f0666@gmail.com> Date: Thu, 2 Nov 2017 17:38:52 +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: 8bit 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 16:38:45 -0000 On 02.11.2017 17:31, Warner Losh wrote: > > On Wed, Nov 1, 2017 at 11:28 PM, Michal Meloun > wrote: > > > > 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 > > > To be extra sure, have we tried to back out this one change against the > tip of -head to confirm? It's pretty trivial. > > Warner Yes, sure. r324938 introduces first real usage of aligned data in TLS section and our __libc_allocate_tls() cannot handle this fact. See https://reviews.freebsd.org/D12907 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 > " > > > _______________________________________________ > 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 > " > >