From: wangkefeng.wang@huawei•com (Kefeng Wang)
To: linux-arm-kernel@lists•infradead.org
Subject: Linux kernel 4.1 boot on arm64 stuck in cpu_do_idle
Date: Fri, 18 Mar 2016 15:08:58 +0800 [thread overview]
Message-ID: <56EBA98A.90306@huawei.com> (raw)
In-Reply-To: <DB5PR04MB21663013F59C3F0DA1FBFB41F88C0@DB5PR04MB2166.eurprd04.prod.outlook.com>
On 2016/3/18 14:26, Sakar Arora wrote:
> Hi
>
> Trying to boot custom kernel 4.1 using UEFI bootloader. Using debugger it is seen the PC is in the cpu_do_idle function inside proc.S (the stack traces the call to rest_init() function)
>
> It seems that the init process is not getting scheduled. Can somebody suggest a debug strategy for this?
1) check the configuration of uart8250, like interrupt in dts.
2) check gic in uefi, I met similar situation ago,
it leads to lost interrupt, due to the wrong configuration of gic.
3) time issue ?
BRs,
Kefeng
>
> Thanks
> Sakar
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> .
>
prev parent reply other threads:[~2016-03-18 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 6:26 Linux kernel 4.1 boot on arm64 stuck in cpu_do_idle Sakar Arora
2016-03-18 7:08 ` Kefeng Wang [this message]
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=56EBA98A.90306@huawei.com \
--to=wangkefeng.wang@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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