Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3043641imu; Fri, 18 Jan 2019 03:55:36 -0800 (PST) X-Google-Smtp-Source: ALg8bN5QcRqpT+0bPM7mEf8Do2DyWzCpW6uubQm6Em9BXqW9iPxHdTh0U1jeRclPgw1pSGQaU+k1 X-Received: by 2002:a17:902:e28e:: with SMTP id cf14mr19199637plb.311.1547812535940; Fri, 18 Jan 2019 03:55:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547812535; cv=none; d=google.com; s=arc-20160816; b=0nRo/t87QvUfGKYzpV6ubK5pUKd89zqAauiNfss/3CmSdwGBOcYVIws7KLPpV6D0ee ffqW68ZWBHst2ZmDRaU6Drktj1B/DU9wef8hsfR8AvyqQzc2FK2kxGG6uqcU1Fw10rNv PDq12uBsUwZm3E0gz2LWkBKqtYSWzA9lqUXdYEvbUS6w2GK0qvFCoh6PiYdKd7CZ4DZ7 E9PTkaPFOAnSn9fJxxO9tDXhsXDwL8t4eiRI/U1FYAQAoPpPnW79M89Swzru7G6kZ1Kw rtLeodEJXuhfi4A+OczyMIgYewZ+fI9OaFic9gdan9O+zGjJbVrEaK39t/desjXMDODh eTVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature; bh=6Z03m39yVN7WHT46pNdXe7MKkVPVuwBoq9TKVrgdgio=; b=MerWf9VlCyecNTkWu4gGbU5Xq6tx+h49eGhLjmKL8qbz2pRAZnIYnY57wOsMAHTzg9 bZeCL2Xc2uasKd+M9dvJmKxJDl5/wIS5xVRLL4j8XSkY64xwC/Hq1uhSxZ3CXMTnlHbF udW2KYhCiH5NOcTMh2BL+stQeA1KBrp8VVR2kXplXG0MPKklR5bGqjKjYDbLWes3n+ry a/tFbXEtOPedCI6NutgWd78Tkq4eQ57TZU9SOZyjF6i6YCXTL5I2ynOkjwZCyZ/rcxNp RxbYxO2b6M2CbvastsDRAFdra/4JKtc/kG8WczZx8uLqzYEffk/OnDKgywtq6tDlAscr Kc5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=Et070cH1; dkim=pass header.i=@codeaurora.org header.s=default header.b="LNIV/M4J"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b5si4444407pfg.121.2019.01.18.03.55.20; Fri, 18 Jan 2019 03:55:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=Et070cH1; dkim=pass header.i=@codeaurora.org header.s=default header.b="LNIV/M4J"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727467AbfARLxs (ORCPT + 99 others); Fri, 18 Jan 2019 06:53:48 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:53182 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726810AbfARLxs (ORCPT ); Fri, 18 Jan 2019 06:53:48 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 78E846084F; Fri, 18 Jan 2019 11:53:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1547812427; bh=5pVPmFdQ3w2BGxaeu0magkeFtuoC9f4C2CrM52TYAzI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Et070cH1hI1/9PRKE7GCYZCNczeDnwcISg6ZwqwFN+Z/qV/dRSJc/FiD6xk9oCOXb fMbVkhba6OeYDG06bzZPuzBF03RCwhYqXAEDSpfCtXgItjjJbeYjSfQkrCWLkTs0bl pPzCZqCBLNQVYZvfDzgpBtNxiacytE93YnCOGwmM= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from [10.79.129.0] (blr-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.18.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: saiprakash.ranjan@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 9A5146053B; Fri, 18 Jan 2019 11:53:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1547812426; bh=5pVPmFdQ3w2BGxaeu0magkeFtuoC9f4C2CrM52TYAzI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=LNIV/M4JkJiVdnvn42KYtyWY1fuNnOQckn0b4msCvaP70DskszhcNj5mAuLxVl3Is DnMgmIAZXIPaitUWdxWp6UAEIfhyZCUI2ZpjBelKTsAdTPioTKohDR+Yurzfr6nShR LH2vQyfWjMqe+44Z+xAiFuuyL7w+3T2n3MEetPJI= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 9A5146053B Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=saiprakash.ranjan@codeaurora.org Subject: Re: Need help: how to locate failure from irq_chip subsystem To: Pintu Agarwal Cc: open list , linux-arm-kernel@lists.infradead.org, Russell King - ARM Linux , linux-mm@kvack.org, linux-pm@vger.kernel.org, kernelnewbies@kernelnewbies.org References: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> From: Sai Prakash Ranjan Message-ID: <1ffe2b68-c87b-aa19-08af-b811063b3310@codeaurora.org> Date: Fri, 18 Jan 2019 17:23:42 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: 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 On 1/18/2019 4:50 PM, Pintu Agarwal wrote: >>>> Could you please tell which QCOM SoC this board is based on? >>>> >>> >>> Snapdragon 845 with kernel 4.9.x >>> I want to know from which subsystem it is triggered:drivers/soc/qcom/ >>> >> >> Irqchip driver is "drivers/irqchip/irq-gic-v3.c". The kernel you are >> using is msm-4.9 I suppose or some other kernel? >> > Yes, I am using customized version of msm-4.9 kernel based on Android. > And yes the irqchip driver is: irq-gic-v3, which I can see from config. > > But, what I wanted to know is, how to find out which driver module > (hopefully under: /drivers/soc/qcom/) that register with this > irq_chip, is getting triggered at the time of crash ? > So, that I can implement irq_hold function for it, which is the cause of crash. > Hmm, since this is a bootup crash, *initcall_debug* should help. Add "initcall_debug ignore_loglevel" to kernel commandline and check the last log before crash. - Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation