kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Pintu Agarwal <pintu.ping@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	linux-mm@kvack.org, linux-pm@vger.kernel.org,
	kernelnewbies@kernelnewbies.org
Subject: Re: Need help: how to locate failure from irq_chip subsystem
Date: Fri, 18 Jan 2019 15:54:33 +0530	[thread overview]
Message-ID: <bceb32be-d508-c2a4-fa81-ab8b90323d3f@codeaurora.org> (raw)
In-Reply-To: <CAOuPNLj4QzNDt0npZn2LhZTFgDNJ1CsWPw3=wvUuxnGtQW308g@mail.gmail.com>

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] [<ffffff9469f8d2e0>] __ipipe_dispatch_irq+0x78/0x340
> [    7.253469] [<ffffff9469e81564>] __ipipe_grab_irq+0x5c/0xd0
> [    7.341538] [<ffffff9469e81d68>] 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?

Thanks,
Sai

-- 
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

  reply	other threads:[~2019-01-18 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 10:08 Need help: how to locate failure from irq_chip subsystem Pintu Agarwal
2019-01-18 10:24 ` Sai Prakash Ranjan [this message]
2019-01-18 10:48   ` Pintu Agarwal
2019-01-18 11:03     ` Sai Prakash Ranjan
2019-01-18 11:20       ` Pintu Agarwal
2019-01-18 11:53         ` Sai Prakash Ranjan
2019-01-21 12:35           ` Pintu Agarwal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bceb32be-d508-c2a4-fa81-ab8b90323d3f@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=pintu.ping@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).