Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2987525imu; Fri, 18 Jan 2019 02:50:26 -0800 (PST) X-Google-Smtp-Source: ALg8bN5B0y5hQpX/efX6K/3BICmWQBwftTplGncBhxmNvxbFYbAjzLRrbZ/UIiTuwwxTEbvZmJXV X-Received: by 2002:a63:2315:: with SMTP id j21mr17214391pgj.297.1547808626877; Fri, 18 Jan 2019 02:50:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547808626; cv=none; d=google.com; s=arc-20160816; b=i6bKhkBzSm4lQNHZmbbhwXGMHeqZI4jzhdAPhIhWa3X1/GgrgVKF+EEpxU0QCNxrqI D8cf4wM/Cs5xIV2rTuXcFhRlPT8lWAIEk6r5jhsTa6e59cw/WgwO4fTO+y7WkIMKfnA3 +YkQ/T4g8ktBy3qzqVomvYsx91BXF0Qwb/ZiS1O9wRBAQG3DJjj+tGNMzkuBiqhNz9RD niB/bKVsmZZmixF4z6KvhE1Mr9fvyfjvrCD6zt8Wp2xxnR5lOHdLRPvOnxs2zzOLeaIY q4p53XW2Dj0ji7Zg2noXqbHXxZwEnU3vvElD2Pkdn+RtWyyCGecakqDRvFymAXbGI6h1 QAsg== 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=/6xliivq0weCXLfwCUUU2y3nNNwTp933/QmOo/bU0eY=; b=kL29B+ND7hAAPGeHGTLOMUaQGk2FSWQdQrm/tzMfrKFCCboGafGlFXMC6ORLCWWC5Y sGJi1XbP1Aw6/lHJB5rtHOf1BBila70zxOXhM0iIQxjuWMZDfFHU2IEBOvRLcbIYeJfT O/Gr0wtf+HG03p2UXRJDeLSs6/8ZTVGk29/i6+zo5XHAlscykhwlMidrTxjixrUQUqaQ YkKJZR5lGo2yeoNsHS/u9+kn5GwenLDJ1XwlA2XnfLtoLeaX6pzqaOXv6kw+GM09ZG/e wsXgreGbP4QSiMR2EtNMqK+JjZKkfJu+GEy05li4ebIl2EYO8TklXfDWSVlfLheQHooF +fzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=C6MnRUdv; 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 p3si4698919pgi.0.2019.01.18.02.50.08; Fri, 18 Jan 2019 02:50:26 -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=C6MnRUdv; 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 S1726896AbfARKsp (ORCPT + 99 others); Fri, 18 Jan 2019 05:48:45 -0500 Received: from mail-vs1-f67.google.com ([209.85.217.67]:41956 "EHLO mail-vs1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726416AbfARKsp (ORCPT ); Fri, 18 Jan 2019 05:48:45 -0500 Received: by mail-vs1-f67.google.com with SMTP id t17so8129613vsc.8; 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=At48QkHYVBHDt9gVQQ3YXMNtdPYrLdFrYFMWvsVqginPkaKHXZ/S0qEdb3wWX3ExAB yeUVOD5qkVMkgAM6WNlj2EqUQPxmvVxx4t30N3bcFKiw8K4sngW+ZqMe3ykoRKuw5FXF UNznfr9VzV2OQMTgjZwyN6To9RMfDzSe0w4YYMNC61Ui1KXq07zZCmDW+H25F43aogXE KnXNaNlQ5qHYHv/2TlgbxHlv+PzKV7GRoKlOwwn/cx7sG8mRk25tNU1unKWh7HsSIeMW cawxLrlTr/doCBFBaGIDe7WRltZWWhrNmj19tIdZO/D/P/wICszUVmuVWz+QiZykNDtk 9PPg== X-Gm-Message-State: AJcUukeF68imL5RzxGrVjvVy/OZPs5XPTFPsEP4bc1F7bJex1Yt1p/Jt OYIC6nOkTTEEC7Ugb3qkQ0HFpCTa9Y4dfk1bWME= 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: 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 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