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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham 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 0498EC43441 for ; Tue, 13 Nov 2018 09:44:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B9E5122360 for ; Tue, 13 Nov 2018 09:44:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linaro.org header.i=@linaro.org header.b="FILr73Wh" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B9E5122360 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731892AbeKMTln (ORCPT ); Tue, 13 Nov 2018 14:41:43 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:50306 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731526AbeKMTln (ORCPT ); Tue, 13 Nov 2018 14:41:43 -0500 Received: by mail-wm1-f68.google.com with SMTP id 124-v6so11258953wmw.0 for ; Tue, 13 Nov 2018 01:44:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Z20JIB3gJ+gh+yYViOz3RE32gSmIlwOSaEriEYIZy+s=; b=FILr73WhVYLvD6gePeRbe5kQkcQNlaaY55Z6WLtuBC6LZuG1UcMpCK6NfNHgZoJsEr 03bT0oLq9/27dHwzkjkoZXoCNgiCyVRcAzYBQjBzAmlab37rKpsoAkIm+njsTvPWFF12 ckUZXkUhewNaUIsiDOeYPqj9rYLx2+i9oP0Hc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Z20JIB3gJ+gh+yYViOz3RE32gSmIlwOSaEriEYIZy+s=; b=oT9SObL0rkC0HKFUdU9XqqnrwWcYhWuy6xRyXB5HHRf9IOWozbAOVtZ8SfLDL7f1Ey e1UOO9CqO6Zr4Dy7d1KvyfzufGDYTzcNBaqZGlo8Vw0dc+mQKsrCTLhdq7cv0+mnRWzj 2eKgh1OF+dT8rGDZdx63ka6rdaaTH4kpwCZpTu4i29H1lcUka59+kwlIcAa601xC/c2C UrZtETo5nWzaqcvouDWhz08Cbs/5waYPFwxHefyHWHnVWx5lNTp5P9gkbLf39KhNekPN vu58abSNf9jWJh6CFKaBb4188bOxSI3ZtJE2Kl+MAE+3HW9Dhsy2QAH/YXaJdQGA0qej WZLw== X-Gm-Message-State: AGRZ1gJbavIAu10ZHEDu9jz9fS1KXPSuD6Qm9bLcLS7YuQuy0LdUTOaB hvPMZhVNIsplzRKew9asJzAd+Q== X-Google-Smtp-Source: AJdET5dpVTTgP5t9Sj3bo82G8eM+RBM8FM+sdkY05jJF5/enuWz+ZzbmUMkP+cYLjtlMYYqeqftsUA== X-Received: by 2002:a1c:c10b:: with SMTP id r11mr2488917wmf.84.1542102264007; Tue, 13 Nov 2018 01:44:24 -0800 (PST) Received: from [192.168.0.19] (cpc90716-aztw32-2-0-cust92.18-1.cable.virginm.net. [86.26.100.93]) by smtp.googlemail.com with ESMTPSA id u14-v6sm22508004wrs.27.2018.11.13.01.44.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Nov 2018 01:44:23 -0800 (PST) Subject: Re: Crash in msm serial on dragonboard with ftrace bootargs To: saiprakash.ranjan@codeaurora.org, Steven Rostedt , Stephen Boyd Cc: Joel Fernandes , Bjorn Andersson , Andy Gross , David Brown , Jiri Slaby , Kees Cook , Geliang Tang , Greg Kroah-Hartman , Pramod Gurav , linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, Rajendra Nayak , Vivek Gautam , Sibi Sankar References: <472db11e-49a6-a1ee-e298-791ee1bbb10b@codeaurora.org> <20181016141610.639b9000@gandalf.local.home> <20181016144123.24c47b38@gandalf.local.home> <7781815e-cba2-9e36-db6d-268298747876@codeaurora.org> <20181016150328.3450d718@gandalf.local.home> <20181017223334.29ca2837@vmware.local.home> <58d2474c-53cd-e6cb-2d25-db38d1a88da6@codeaurora.org> <20181018091706.62310b38@gandalf.local.home> <20181019041740.GB141835@joelaf.mtv.corp.google.com> <8a75f2d5-f1bd-504e-b545-ae2e2f61ca8f@codeaurora.org> <20181019095122.0f1c0946@gandalf.local.home> <9cafe321-87f6-98a3-3bda-c2f7a3d7fc67@codeaurora.org> <20181019111205.5c8e98e8@gandalf.local.home> <1e6cc1fa5263b9edfcf7567d3f9f65fd@codeaurora.org> From: Srinivas Kandagatla Message-ID: <38099043-f5ed-6d81-bf94-13f61cfa8507@linaro.org> Date: Tue, 13 Nov 2018 09:44:22 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1e6cc1fa5263b9edfcf7567d3f9f65fd@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sai, On 25/10/18 15:36, saiprakash.ranjan@codeaurora.org wrote: > "If I disable dma node and LS-UART0, then I don't see any crash and > ftrace also works fine" > > And one more observation is that even without ftrace cmdline, if I use > earlycon and disable dma, I face the same crash. > > So basically this seems to be some kind of earlycon and dma issue and > not ftrace(I can be wrong). > > So adding Srinivas for more info on this dma node. Its Interesting that my old email conversations with SBoyd show that I have investigated this issue in early 2016! My analysis so far: This reason for such behavior is due the common iface clock (GCC_BLSP1_AHB_CLK) across multiple drivers(serial ports, bam dma and other low speed devices). The code flow in DB410C is bit different, as the uart0 is first attempted to set as console and then uart1, this ordering triggers pm state change uart_change_pm(state, UART_PM_STATE_OFF) from serial core while setting up uart0, this would go and disable all the clocks for uart0. As uart1 is not setup Yet, and earlycon is still active, any attempts by earlycon to write to registers would trigger a system reboot as the clock was just disabled by uart0 change_pm code. This can even be triggered with any drivers like spi which uses same clock I guess. Hope it helps, Either earlycon needs to reference the clocks or those clocks needs to be marked always-on (but only with earlycon). > > Also just for a note: apq8096-db820c.dtsi shows UART0 is disabled because > bootloader does not allow access to it. Could this also be the case for > db410c? No, this is not the case with DB410c. DB820c has added restrictions in TZ, I think new booloaders should have solved this issue. Thanks, srini