Re: Can printk in the root domain cause the system to hung ?

2021-04-28 Thread Jamie Huang via Xenomai
On Tue, 27 Apr 2021 18:36:02 +0200 Jan Kiszka 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.

Re: Can printk in the root domain cause the system to hung ?

2021-04-27 Thread Jan Kiszka via Xenomai
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

Can printk in the root domain cause the system to hung ?

2021-04-27 Thread Jamie Huang via Xenomai
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

Can printk in the root domain cause the system to hung ?

2021-04-27 Thread Jamie Huang via Xenomai
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

Can printk in the root domain cause the system to hung ?

2021-04-27 Thread Jamie Huang via Xenomai
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