From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 566D6C433EF for ; Tue, 21 Sep 2021 21:49:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 432A460F3A for ; Tue, 21 Sep 2021 21:49:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235661AbhIUVvV (ORCPT ); Tue, 21 Sep 2021 17:51:21 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:42574 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235527AbhIUVvP (ORCPT ); Tue, 21 Sep 2021 17:51:15 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 18LLnbOk034521; Tue, 21 Sep 2021 16:49:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1632260977; bh=qmFLuf8btJCpkABZQ3txkEnQak00qK8uLJahKxWnQjA=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=GwuPbp2ybGVHuAGF60WXCNN1nWvYfoyiuoFHtX+hSSmyCSH7SgbiKF5zaYayN2lGF o5XmiSv57OifNiMrymuztHkRZIt22lmO9e6TulWS+bf3HoXPLyJWhqPoHHsrSUn91h gnwZ6Xh/VEEKihBs2VPFyzwbZ/wC1VS3WG7fnJec= Received: from DFLE109.ent.ti.com (dfle109.ent.ti.com [10.64.6.30]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 18LLnbrv049877 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 21 Sep 2021 16:49:37 -0500 Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14; Tue, 21 Sep 2021 16:49:37 -0500 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14 via Frontend Transport; Tue, 21 Sep 2021 16:49:36 -0500 Received: from [10.250.37.219] (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 18LLnaPk123879; Tue, 21 Sep 2021 16:49:36 -0500 Subject: Re: beaglebone black boot failure Linux v5.15.rc1 To: Drew Fustini CC: Tony Lindgren , Matti Vaittinen , Grygorii Strashko , "Vaittinen, Matti" , "linux-omap@vger.kernel.org" , Paul Barker , Peter Ujfalusi , =?UTF-8?Q?Beno=c3=aet_Cousson?= , "linux-kernel@vger.kernel.org" References: <120a0ca4-28c7-5a7b-f1ab-2015c8817bda@fi.rohmeurope.com> <0679a5bb-88d1-077d-6107-d5f88ef60dbf@fi.rohmeurope.com> <8f3963ca-ff09-b876-ae9e-433add242de2@ti.com> <331ab81e-cd42-7e9b-617a-fde4c773c07a@ti.com> <615b6fec-6c62-4a97-6d0c-d2e5a5d1ccb2@fi.rohmeurope.com> <36785ccf-57b4-eaf1-cfc0-b024857f7694@gmail.com> From: Suman Anna Message-ID: <40077cea-1f5e-de67-58dd-7fae0f63678d@ti.com> Date: Tue, 21 Sep 2021 16:49:36 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/21/21 3:29 PM, Drew Fustini wrote: > On Tue, Sep 21, 2021 at 9:09 AM Suman Anna wrote: >> >> Hi Matti, Tony, >> >> On 9/21/21 2:47 AM, Tony Lindgren wrote: >>> * Matti Vaittinen [210920 08:23]: >>>> Finally, adding the udelay(100); (as Tony suggested) at the end of the >>>> omap_reset_deassert() did make the oops go away even when pruss_tm was >>>> enabled. I don't know what would be a proper fix though. >> >> I have been able to boot v5.15-rc1 just fine on my BBB without any additional >> changes [1]. >> >> May I ask what is your BBB board version? My board is rev.A5C. > > That rev is quite old [1]. Would you be able to try a Rev C? It has > been in production since around 2014 with the move from 2GB to 4GB > eMMC. I don't have any rev.C boards handy to try. I am curious to see if there is some correlation between failures and board versions. I see that there is a minor processor change to AM3358 from rev.B onwards compared to the AM3359 that I would have on my board. PRU-ICSS IP would be present and supported on both though. regards Suman > > Thanks, > Drew > [1] https://elinux.org/Beagleboard:BeagleBoneBlack#Revision_A5C >