From owner-freebsd-arm@freebsd.org Fri Nov 3 16:21:36 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 8A85FE55B88 for ; Fri, 3 Nov 2017 16:21:36 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 325806AB3D for ; Fri, 3 Nov 2017 16:21:36 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id w105so2982894wrc.0 for ; Fri, 03 Nov 2017 09:21:36 -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=ydzPg+UuCPytpX0pQydwHlkCIGrXFArPRBC01GcNOv8=; b=aNCUsxhjmvcUmOeDFegI67tb0lLqVvBUjytr6X5oqiMb+XepX/JL0ckVab8onhq+bV gKYMMoYfaXZchTpjDae90x2wdTLSJQZ+tJS0joapi7wIgjBSKQvhARSYRFQh5JEdQw2+ 76gaEAxlQkl6JkuVQtLBFVVOC26+gFUWlmlXVb95e9jSfrb4PnKMp6NCT+1Rrx9dFEY5 xmRDayH6wghWiwiGPM0FOp+Evp2/47ROaaGU77vrtCq2z0gRW/SuGrdNHxoGwtL4NGpP DW6FQoefzQwDhq9sVbzpAjX/Y8ecv0mNsM/b1AzgIv9aGp3oy7GbAtRm6wpxQKEhRDIt woeQ== 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=ydzPg+UuCPytpX0pQydwHlkCIGrXFArPRBC01GcNOv8=; b=AUl6ovAOKZfEZA/BBkj395KVkoRe9hbtIWal4cZPmxe2iyYb9jeWUi7OQ72LYaxaSu UOtOrqjN+vdZAnjSbK/sw+IE0+EVa6jU+wUg0FM7YFAZHp/79KTY3A9EgC1F67UcdjjS Sli2AjUuZmIeCvE7J95FJ9GvifcziNDmDOcQcr8QnzYPTJzQQLJvHLiyqDS5x+666U/J 8hzhiOk0i9arYvIGJbwqXnRfAQHjfXsvYim9sEvHhEjuhij9Wargz261bUtPjedjW/jU h6LEr73FcUTBjorQ8JcYNHVdLPbqGjNM4PQ1XjpCbO4d1EsB5o058NR60e6tEZdAQu4/ eRtA== X-Gm-Message-State: AMCzsaUeCqTsAExGtV6AMoTyL9YY4RDaDDmoKCtvXRP4V3WdQXksefA4 xN8dpVK5ePS0alZYQyIvrcxGEFRC X-Google-Smtp-Source: ABhQp+RPNBmWlOyyCmpQ2aPTLxVwPBhr5hVrryWHxnd2qlk0hHHuVd5AQJgf8O2mqputI9FgWe3Xsg== X-Received: by 10.223.163.22 with SMTP id c22mr6188825wrb.73.1509726094254; Fri, 03 Nov 2017 09:21:34 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id h66sm2336740wmd.11.2017.11.03.09.21.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Nov 2017 09:21:33 -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: <9fea2c49-585b-d280-8aa7-6c3edf649b83@gmail.com> Date: Fri, 3 Nov 2017 17:21:46 +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: Fri, 03 Nov 2017 16:21:36 -0000 On 02.11.2017 17:35, Kyle Evans wrote: > On Thu, Nov 2, 2017 at 11:31 AM, 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/67ea3325c50770b5031ef02882b2dc > > > cdd1f7611f > > > > 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 > > > For what it's worth: I didn't try backing out the change, but I can > confirm that the above-mentioned patch does fix it -- I applied it just > a bit ago.  I just committed this, so current after r325364 should be again usable. Michal