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=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 6E7E8C43444 for ; Fri, 18 Jan 2019 11:03:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3F16020823 for ; Fri, 18 Jan 2019 11:03:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="aU1RNtXI"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="btomFqtr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727143AbfARLDp (ORCPT ); Fri, 18 Jan 2019 06:03:45 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:39990 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726952AbfARLDp (ORCPT ); Fri, 18 Jan 2019 06:03:45 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 4ACF260585; Fri, 18 Jan 2019 11:03:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1547809424; bh=PhjT21x99jC/rTs24SyBERZkJQM6E90FddkK6U6LlsQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=aU1RNtXIFHOOrxfJWlmrS6kntKEy3PrcJQAO5/HLVI9Rkvze7ip6X4sWej7ZqtQfB L0dDmA442FSPQizgl2hfcvGGAeEzKuR9HenaRKG249yty7lMmL+lS1oNctV1MAp3O0 k1z6Sqhk6b5SfPUlBli+vPfYrGVg8utSQyMiVwAo= 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 3E7FB6055C; Fri, 18 Jan 2019 11:03:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1547809423; bh=PhjT21x99jC/rTs24SyBERZkJQM6E90FddkK6U6LlsQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=btomFqtr28zFI9ZOzrC55JgNXBbfBN7n2m3JyKmL3y8XxJqPIJQ1kdprppIXV6N95 sDNVvtN6RdNtPYmKMi3gUwKtCVYewSm43Wg8KnfrlS0+ncOLvkrWT2s6bSFCOdn5f9 ssjAGjfnXXb/8MgfZ+eijBL79jSyuXIsIRShkeTU= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 3E7FB6055C 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: From: Sai Prakash Ranjan Message-ID: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> Date: Fri, 18 Jan 2019 16:33:38 +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:18 PM, Pintu Agarwal wrote: > On Fri, Jan 18, 2019 at 3:54 PM Sai Prakash Ranjan > wrote: >> >> Hi Pintu-san, >> >> On 1/18/2019 3:38 PM, Pintu Agarwal wrote: >>> Hi All, >>> >>> Currently, I am trying to debug a boot up crash on some qualcomm >>> snapdragon arm64 board with kernel 4.9. >>> I could find the cause of the failure, but I am unable to locate from >>> which subsystem/drivers this is getting triggered. >>> If you have any ideas or suggestions to locate the issue, please let me know. >>> >>> This is the snapshot of crash logs: >>> [ 6.907065] Unable to handle kernel NULL pointer dereference at >>> virtual address 00000000 >>> [ 6.973938] PC is at 0x0 >>> [ 6.976503] LR is at __ipipe_ack_fasteoi_irq+0x28/0x38 >>> [ 7.151078] Process qmp_aop (pid: 24, stack limit = 0xfffffffbedc18000) >>> [ 7.242668] [< (null)>] (null) >>> [ 7.247416] [] __ipipe_dispatch_irq+0x78/0x340 >>> [ 7.253469] [] __ipipe_grab_irq+0x5c/0xd0 >>> [ 7.341538] [] gic_handle_irq+0xc0/0x154 >>> >>> [ 6.288581] [PINTU]: __ipipe_ack_fasteoi_irq - called >>> [ 6.293698] [PINTU]: __ipipe_ack_fasteoi_irq: >>> desc->irq_data.chip->irq_hold is NULL >>> >>> When I check, I found that the irq_hold implementation is missing in >>> one of the irq_chip driver (expected by ipipe), which I am supposed to >>> implement. >>> >>> But I am unable to locate which irq_chip driver. >>> If there are any good techniques to locate this in kernel, please help. >>> >> >> 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? - Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation