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 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 5F5ADC43387 for ; Fri, 18 Jan 2019 10:10:33 +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 0CB6320855 for ; Fri, 18 Jan 2019 10:10:32 +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="GP/PM6Kz" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0CB6320855 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 1gkR6C-00081W-DQ; Fri, 18 Jan 2019 05:10:04 -0500 Received: from mail-vs1-xe42.google.com ([2607:f8b0:4864:20::e42]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gkR69-00081E-3R for kernelnewbies@kernelnewbies.org; Fri, 18 Jan 2019 05:10:01 -0500 Received: by mail-vs1-xe42.google.com with SMTP id t17so8072716vsc.8 for ; Fri, 18 Jan 2019 02:10:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=n+bIrCa8NP47kNy2c+LBCkgyAzNBjMr/5OaE8AJS908=; b=GP/PM6KzhJ5mgHy2MpFiP6V/3Z8fWtWIr7ui26qnGnpyJsgMQsmhG9DPGZJPiGsE8y E8MnNBGPBrwMqH5IUF6GdeVgCv8Si72pSI2Oivu5uZfmtkFisV4SbfFKsbgs1iLEVvkd NbO61JySwPVYSS87fy+jBN2JeaLp5F1nWMOnzyxBvAzEmF+lgIRl7Ix/dydoLUjbYutS Es4zpm7QZHGaurBWOubVTy5C/RKcyl7jX091TgKXES0m3tv4NeZpXVcBFdX04m7C479m K+kSbxTk/G5nK0KdyEaFtf2PcAKTvtX9kjgVgq2Gy4lnOSn/d+hhqei9GQUyPqZM7U54 Gs4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=n+bIrCa8NP47kNy2c+LBCkgyAzNBjMr/5OaE8AJS908=; b=gO836yn4wIJkZHrszFptzfLvQir9deC7C80PYFX7McYF7xYRqkpp2VGxGzMjmVHfWg gNdFk07JkEpMHxdwJTpE02pqWABU/1YuULFrGpdVP+B4Zpdjp84OmluKmbXbCvyql84N Arne1AGcqZtNVzrl3b+OJQngc/sIVYnAEccLawLSBeLjelxiCoT0/DUKg5ksFiD/LZLT wLXfp59XrJGcsww0ky8gWFephVxV4ymyPh24LcOemPZlXqkwy5EsWpdaQG+ab4wwaqMS 3nXpW/wO0TNHi+cM6qsOzHcTfZxxAAvcEvm3UwWNQQ9LpJrbQqU4/OpcUSTjr2LgtJ4s 52Tg== X-Gm-Message-State: AJcUukeTdRKYnEIysmIu3VZH6B/kBHJfK/54KHUVbcL2q/uOqysCZc+j ipZgE1tIXuO5KTJ0QrQNsflQ74ldflSktK1+IpY= X-Google-Smtp-Source: ALg8bN5YAP4roDEn+VCrnUhEOEhDQm7xkOO6as2Vt9tet88KRpdW6e+snTl+r440Vp8Jgg3+wEYVTqV3MCJNe50mcQQ= X-Received: by 2002:a67:f793:: with SMTP id j19mr6892160vso.196.1547806139093; Fri, 18 Jan 2019 02:08:59 -0800 (PST) MIME-Version: 1.0 From: Pintu Agarwal Date: Fri, 18 Jan 2019 15:38:48 +0530 Message-ID: Subject: Need help: how to locate failure from irq_chip subsystem To: open list , linux-arm-kernel@lists.infradead.org, Russell King - ARM Linux , linux-mm@kvack.org, linux-pm@vger.kernel.org, kernelnewbies@kernelnewbies.org, Pintu Kumar 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 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. Thanks, Pintu _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies