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_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 824D8C43387 for ; Fri, 18 Jan 2019 10:48:59 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3D969204EC for ; Fri, 18 Jan 2019 10:48:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="C6MnRUdv" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3D969204EC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1gkRhe-0008Sj-OY; Fri, 18 Jan 2019 05:48:46 -0500 Received: from mail-vs1-xe43.google.com ([2607:f8b0:4864:20::e43]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gkRhc-0008Sa-Pu for kernelnewbies@kernelnewbies.org; Fri, 18 Jan 2019 05:48:45 -0500 Received: by mail-vs1-xe43.google.com with SMTP id p74so8162009vsc.0 for ; Fri, 18 Jan 2019 02:48:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/6xliivq0weCXLfwCUUU2y3nNNwTp933/QmOo/bU0eY=; b=C6MnRUdvpvjVi5Kc8Lceq9DKjFe5J546YEJCUr3Sbn1TcFwfxAzTWbjASQrCNA6aGh Nu/6WGPZxYRxA/SP6he88jxtClUyBRL+kl2le9yc41CozxPqdcpzZtFWFFtmSk9q/IrS HHahJkKxV2iH2vPXAwYh3qMunjbO0J2LEhLf8NG3QzP8ns6wtmr5u32u7kKLP3eWButc TZ8XelSo1gGw4j3PnEwKa80b1ml+h4JXNIkIuun5HIV0fRllQsNUfe7GN9YlNKAObGGo kM32yguM1ceiCrAWAVr68YUwEHv2cai2UhJ0xo8+YTnRF8yU+9/mncUtqtLonPnGQH8M kfng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/6xliivq0weCXLfwCUUU2y3nNNwTp933/QmOo/bU0eY=; b=oAkjWPQgUfjn3IyHXtHv67+9w5s1sU775K1qIIYEoH273IfzyZeUo9IoiJvWASDN9T NsETG32GwkuFpu2LgyfOFrmHMbkqJKd1osF4zFuUzPE9GGiEVO3y3tHQXaoN4P4bE66H uC8gLIzwaBNV7GzUogTPny1rxmekYwLgRte44Jx6tiQytQrWqj8SI5vZ8+UvMXg+tfHs OnVjKg9pyi3ZcDXr9rWJ6GRJxRzNWgzmWHuVx8Kbk5CV2TRpTIbQOjtNyCMxkrkGZq0E Fj5s1TY1/GpXZgCVxzT+qokELIDySFYSwS+c70tabnaGuFPlqTLDm2y+UUVcW5ueGtoJ Ad/g== X-Gm-Message-State: AJcUukeX+OIS+bp6cpq/Gug1yyGkXgOf/HL9a0l/ycUFnqnYgt/j8WQM S/6p32Mv97bvgpKizxkKrvU3UAEq56qV2PWFn8Q= X-Google-Smtp-Source: ALg8bN7HsppUgj5spIWajytKcejIfmTNluhxxl0gRonQb5lcTa162V7q5iApGv92T5XidVHBMY1/wVNcnfaji/TcPRo= X-Received: by 2002:a67:f793:: with SMTP id j19mr6934457vso.196.1547808523523; Fri, 18 Jan 2019 02:48:43 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Pintu Agarwal Date: Fri, 18 Jan 2019 16:18:32 +0530 Message-ID: Subject: Re: Need help: how to locate failure from irq_chip subsystem To: Sai Prakash Ranjan Cc: linux-pm@vger.kernel.org, kernelnewbies@kernelnewbies.org, open list , Russell King - ARM Linux , linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org 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/ > > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member > of Code Aurora Forum, hosted by The Linux Foundation _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies