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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no 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 A4D5DC47083 for ; Wed, 2 Jun 2021 05:31:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 702E160FF1 for ; Wed, 2 Jun 2021 05:31:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229972AbhFBFck (ORCPT ); Wed, 2 Jun 2021 01:32:40 -0400 Received: from muru.com ([72.249.23.125]:35172 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229953AbhFBFce (ORCPT ); Wed, 2 Jun 2021 01:32:34 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 5210080E0; Wed, 2 Jun 2021 05:30:59 +0000 (UTC) Date: Wed, 2 Jun 2021 08:30:49 +0300 From: Tony Lindgren To: Jarkko Nikula Cc: linux-omap@vger.kernel.org Subject: Re: Regression with 6cfcd5563b4f on BeagleBoard Rev C2 Message-ID: References: <68f28473-a196-b106-b4ae-e9162b7002e6@bitmer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <68f28473-a196-b106-b4ae-e9162b7002e6@bitmer.com> Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org Hi, * Jarkko Nikula [210528 13:56]: > My old BeagleBoard Rev C2 stopped booting properly. > > Booting stops "Waiting for root device /dev/mmcblk0p2..." but goes > forward if I feed e.g. ENTER over serial and have to press it through > almost the whole userspace booting. At some point during process it > seems to start working. Perhaps userspace fires some timer etc? Sounds like the beagleboard timer errata handling is either picking a wrong clockevent timer, or later on ti-sysc misdetects the active timer for clockevent and idles it. What does dmesg say in the beginning for clockevent and clocksource timers? > I bisected the issue into commit 6cfcd5563b4f > ("clocksource/drivers/timer-ti-dm: Fix suspend and resume for am3 and > am4"). I used omap2plus_defconfig. OK Regards, Tony