From: Peng Fan <peng.fan@nxp.com>
To: Aaron Marcher <aaron@sigma-star.at>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: RE: Debugging reboot freeze
Date: Mon, 28 Sep 2020 10:07:46 +0000 [thread overview]
Message-ID: <DB6PR0402MB276079E8BC4B302DEE99B58488350@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200928073959.jf5wqgfzirhns6u3@linux-8csb>
> Subject: Re: Debugging reboot freeze
>
> Hi Peng,
>
> > Where do you get the kernel source code and which version?
> > NXP release or Linux kernel upstream?
> >
> > Also ATF/U-Boot version?
>
> - Kernel: Mainline (5.4.66-rt37) + PREEMPT_RT + your power domain patches
you mean upstream stable branch 5.4.66 + RT37 patchset?
Where is the power domain patches? I not did this part.
Do you have a github branch for this? And what kernel config are you using?
> - U-Boot: NXP (2020.07)
NXP official release is 2020.04, not 2020.07, could you share the link?
> - ATF: NXP (v2.0)
Which specific release branch?
Thanks,
Peng.
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource
> .codeaurora.org%2Fexternal%2Fimx%2Fimx-atf%2F&data=02%7C01%7
> Cpeng.fan%40nxp.com%7C18457f343ede453e0b3908d86381b506%7C686ea
> 1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637368756031689583&
> sdata=IZtLBW6a5e87HRspOW5utxsTTehv6E0ZpnRXQDxhOKU%3D&rese
> rved=0
>
> > Do you have a debugger to see where it hangs?
>
> Unfortunately not.
>
> > If you point me your version, and source, I could give a try in my side.
>
> Thanks, let me know if you need anything else.
>
> Regards,
> Aaron
next prev parent reply other threads:[~2020-09-28 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 10:04 Debugging reboot freeze Aaron Marcher
2020-09-27 0:59 ` Peng Fan
2020-09-28 7:39 ` Aaron Marcher
2020-09-28 10:07 ` Peng Fan [this message]
2020-09-28 11:21 ` Aaron Marcher
-- strict thread matches above, loose matches on Subject: below --
2020-09-25 9:57 Aaron Marcher
2020-09-25 15:16 ` Sebastian Andrzej Siewior
2020-10-05 19:40 ` Richard Weinberger
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=DB6PR0402MB276079E8BC4B302DEE99B58488350@DB6PR0402MB2760.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=aaron@sigma-star.at \
--cc=linux-rt-users@vger.kernel.org \
/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).