From: Jamie Huang <jamienstar@163.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org, rpm@xenomai.org
Subject: Re: Can printk in the root domain cause the system to hung ?
Date: Wed, 28 Apr 2021 20:05:09 +0800 [thread overview]
Message-ID: <20210428200509.3a89d2b5@jamie-ThinkPad> (raw)
In-Reply-To: <fa5a2efa-32ff-1386-630b-05099c49a7ff@siemens.com>
On Tue, 27 Apr 2021 18:36:02 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:
Thank you for reply!
> On 25.04.21 12:33, Jamie Huang via Xenomai wrote:
> > Hi, all:
> > We are now porting ipipe on mips architecture. There is a
> > problem, after local_irq_enable() is called in start_kernel(),
> > system looks hung. We found that this may be related to printk in
> > root domain, if we use early_printk instead of printk, the system
> > looks normal and can continue the kernel boot process. Can someone
> > tell me the possible reason, thanks!
>
> Is your code published already?
No, but I think we will publish it when it is basically available.
>
> Also note that the I-pipe architecture is becoming legacy. We are
> moving all archs to dovetail over 5.10 now.
>
> Jan
>
Our kernel version is 4.19, so we choose I-pipe now. We will consider
dovetail if use a higher version of kernel.
next prev parent reply other threads:[~2021-04-28 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 10:33 Can printk in the root domain cause the system to hung ? Jamie Huang
2021-04-27 16:36 ` Jan Kiszka
2021-04-28 12:05 ` Jamie Huang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-24 23:07 Jamie Huang
2021-04-24 12:34 Jamie Huang
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=20210428200509.3a89d2b5@jamie-ThinkPad \
--to=jamienstar@163.com \
--cc=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.