Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3015692imu; Fri, 18 Jan 2019 03:22:14 -0800 (PST) X-Google-Smtp-Source: ALg8bN75nXvc9wqVJQSo3/B8LhcvTBzvCdUtG6LNDHKszej8e+jwKpRCKDJ9SB8G4yKHxWyuoiyi X-Received: by 2002:a63:7e1a:: with SMTP id z26mr16854062pgc.216.1547810534201; Fri, 18 Jan 2019 03:22:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547810534; cv=none; d=google.com; s=arc-20160816; b=rHis3ZVh4O+Dthi1RYoNPUiTJHLN1S9EQh+aDgR/+WDBJPNexWKuaRm2LhJTv7LYBL ZgHf/vSsMWFZcNQlNGHbu8Rdbc9+nNCYR2Xpdxt+N0VnS7i6RhMnniqopaBPh6QQJEWr Vl2ou1glzuGm/LPWWYUm7dbRJ53bpCiuDwqP/CNxFcD6xGIJG8oyMouENuCTs11jDSlG 8Ay8CjF3q0oNWZZj/XhQaWu8l7wY4rjlzBu1fkM8gX3166D9TTRixy9D980ItBQVdUzP vXxQ64sySzrcKQnr3s3hlRpId7UMsZNw0xeVHEUC3GpHOYRZRLOYEojGJt/HdoEthBe6 tJ4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=XqF0zZgFayTmTO/6SUH1t+WrRUcv72SweIyRMBjv87g=; b=OC0qVlXNrjJJDaQhEfnqMFS7e4osIVp2F1merlB03PxDapU1AMKubBklrPqlqF8V8b z0gS3P0EunkWOgnsFi6M3uL8HTHNRYYRPCilLvNmI4X16kcZvr4874SXtmcFZG54qjAh ITMyYSDCjbzf2iFN7X/yHVgRR9RXXkOpZlSAgdQKZGuFjKtjrOUvzgrYzDDX0E9glIbp FdBVytHUu71f5PeL10N8VoMDaLcBs7cGHN7utuIQcHLuwAKA4yJ60Ru0ycduDP32G/0w h5tP3Bl+KC+SXX7ipZjmPbHNYubmzl8+XtGQF8XSk/yIz9nLmO+vO3LdRyd/jYNNv7UJ DeXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=D9GmmFAg; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o7si3953999pgl.42.2019.01.18.03.21.52; Fri, 18 Jan 2019 03:22:14 -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=@gmail.com header.s=20161025 header.b=D9GmmFAg; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726990AbfARLUX (ORCPT + 99 others); Fri, 18 Jan 2019 06:20:23 -0500 Received: from mail-ua1-f45.google.com ([209.85.222.45]:33635 "EHLO mail-ua1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726722AbfARLUW (ORCPT ); Fri, 18 Jan 2019 06:20:22 -0500 Received: by mail-ua1-f45.google.com with SMTP id t8so4570253uap.0; Fri, 18 Jan 2019 03:20:22 -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=XqF0zZgFayTmTO/6SUH1t+WrRUcv72SweIyRMBjv87g=; b=D9GmmFAgjv+5fMxCXp5xCcl/ZSn3HHWyfLbIKnqEUoQGUzpEQtnK872HuAFMporWy8 FtB1I6hgNbsI6BGQyRFD66Jk28nEWyr1cJ54576q1P1tfwswQYlPZtG2LDSNwAGI5c2c vsmRxZ4VggCqcAce4ZGUjJzE0t3BtOo6o6NUmcmENogt0PgUndm2XUv92fNkLoN8XdiF eMhKQ5bgmb3zns4sBO+V0DVEjyLzAeeJ/i1ymIl+iLgWy3i+SBuuwKlGZezyWUgbN7ay NygDllUwwt1jhMga1NQiwO733GITXacZUEs+U3vjLk9yAcGaK99uJ+qO07OWCDuVJ+r7 ksnw== 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=XqF0zZgFayTmTO/6SUH1t+WrRUcv72SweIyRMBjv87g=; b=BZmAcf+NsZHCtKWM1zAVMK1nga+v0Q0svBUZnMT+tNKXvOq8MgQFwdjPwaGTovtnx2 rf70iASJjA7iAP+vync3H37pFoiBaI7eOkuRMrheEaxBI0csJY38Z8ZirQWK7oc94l1z RHOh6NXZpuTgsoARYQzqaOW/7HcFuFBWcUJW76Ul3MYUjm8myY+NgVupPZZ5iVf9KAEc nuGVdHjTZNCNYyXWCZi6g2REq+T4J7jlrQMA1OarqRZAdMJz4n1S6GtFL4TwN/hKi+Au 2l0Cd8Extw55dAAhTYuKAmJnxtliHsSa4BXElte+AtCJdmt/p5N5nILu7/HSzLiWMqBA HP3g== X-Gm-Message-State: AJcUukcppxA8FglbL10TvA6KjgYhSuBrFOvW6ypSOKDifim4fUG47rWs BlaLYRbVL5Z4tx1p/ln2BEC0PhMNzodFouI7HuE= X-Received: by 2002:ab0:8d9:: with SMTP id o25mr7383232uaf.127.1547810421480; Fri, 18 Jan 2019 03:20:21 -0800 (PST) MIME-Version: 1.0 References: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> In-Reply-To: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> From: Pintu Agarwal Date: Fri, 18 Jan 2019 16:50:10 +0530 Message-ID: Subject: Re: Need help: how to locate failure from irq_chip subsystem To: Sai Prakash Ranjan 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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > >> 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.