From owner-freebsd-arm@freebsd.org Thu Sep 24 19:36:40 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1C8BC4260AE for ; Thu, 24 Sep 2020 19:36:40 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f182.google.com (mail-il1-f182.google.com [209.85.166.182]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4By4zp5XtVz45Kl; Thu, 24 Sep 2020 19:36:38 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f182.google.com with SMTP id s88so27540ilb.6; Thu, 24 Sep 2020 12:36:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bN1JikXRM6mu2UHJehtziqpnWewa9m9mMTT5rOB948I=; b=fLu5d5s2ussn13Ohu8hqZIqyyutt/mBAswBylG32HrjiyBF+lB6qu2tTxpRW61ktgO 1bX6olZH2iVZyW2xMhDKh5O72DZuwoKC+PqiKJKU2iUsBz99zxM90F+GhOJT2USjFpuk sJ7pTF8HKuBJ+kFMF/+FHX/5K+Cgo+t4zzgEMrwtPXwBVSCiRyjT+JhbqjPWYL6Rz9W5 S/Q9fnz0WSbm7Mt8fBm/Q7AKLqyiak5Bobk6SiJlQDE8KGq+umSoSQGHU3RZqx3VLJ95 r6B+tLtIOSbGAz7qSI5C0+Mp9bMAMTfnbyw8kozpzTvmTe++fK12EuXx8KMVf6PaieKV rNdg== X-Gm-Message-State: AOAM5312DlO+ynG3NymTe2pcEwdZiuo5c1u1f9P/WmSoVJ3Rmur1l5zk i31evapYJitzEcaeRekozkFTOqEk2jRfht1FNFK+NDm08dM= X-Google-Smtp-Source: ABdhPJx0dS9k7NwzYg6UIdLRCdusCZ7zUqo1ZKT5xPuE80eemZAjKFLLxoGVq5rmUxF7P6AxsiP6tjDcScQhBzeHXsA= X-Received: by 2002:a92:cb0d:: with SMTP id s13mr252261ilo.256.1600976197436; Thu, 24 Sep 2020 12:36:37 -0700 (PDT) MIME-Version: 1.0 References: <202009222004.08MK4xFj037249@mail.karels.net> <8217af510a451f10ea173bf1e26d04dcd50e8ca6.camel@freebsd.org> <1072725987.651720.1600964732891@mail.yahoo.com> In-Reply-To: From: Ed Maste Date: Thu, 24 Sep 2020 15:36:25 -0400 Message-ID: Subject: Re: clock problems with BeagleBone Black on 12.2BETA2 To: Ian Lepore Cc: Oskar Holmlund , "mike@karels.net" , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4By4zp5XtVz45Kl X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.182 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-2.14 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; ARC_NA(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.01)[-1.012]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.09)[-0.087]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.182:from]; NEURAL_HAM_MEDIUM(-1.04)[-1.037]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.182:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; MAILMAN_DEST(0.00)[freebsd-arm]; FREEMAIL_CC(0.00)[yahoo.com,karels.net,freebsd.org] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2020 19:36:40 -0000 On Thu, 24 Sep 2020 at 12:31, Ian Lepore wrote: > > It was mentioned on irc a few days ago when someone noticed the BBB in > the CI setup was failing... > > hrm, looks like BBB has been broken since end of July > panic: Duplicated clock registration: clk@4_0 > ah, mmel r363700 > emaste: im sorry, but this is (unfortunately) expected > collateral damage. im aware of this problem but right solution is not > trivial and it needs more time. > > (strejda == mmel@) > > Then it was mentioned a while later that that BBB is using a very old > u-boot, so maybe that has something to do with it. I've updated uboot on eMMC on the the CI system's BBB to: U-Boot SPL 2020.07 (Sep 24 2020 - 04:58:48 +0000)^M however it's still failing the same way: clk_fixed7: on ofw_clkbus0^M clk_fixed7: Cannot FDT parameters.^M device_attach: clk_fixed7 attach returned 6^M clk_fixed7: on ofw_clkbus0^M clk_fixed7: Cannot FDT parameters.^M device_attach: clk_fixed7 attach returned 6^M ti_clkctrl0: mem 0x14-0x14f on ti_omap4_cm0^M ti_clkctrl1: mem 0x4-0xd7 on ti_omap4_cm1^M ti_clkctrl2: mem 0x4-0x7 on ti_omap4_cm2^M panic: Duplicated clock registration: clk@4_0^M ^M cpuid = 0^M time = 1^M phk@ reported success booting 13-CURRENT snapshots though, so I'm not really sure what's going on.