On 02.06.20 10:51, chensong wrote: > > > On 2020年06月02日 15:49, Jan Kiszka wrote: >> On 01.06.20 15:51, Greg Gallagher via Xenomai wrote: >>> I'm not sure if the rpi4 is in mainline yet but you may have more >>> success trying this with the mainline kernel >>> >> >> The RPi4 is still far aways from mainline, unfortunately. The usual >> downstream mess. > > any thought about "[ 0.712926] irq 38 handler xhci_msi_irq+0x0/0x30 > enabled interrupts " in kernel/irq/handle.c:153? > > call stack is like：irqs_diabled -- raw_irqs_diabled -- > arch_irqs_diabled -- ipipe_test_root > > Not handled msi irq domain(Brcm_MSI) approprately?
Often this means that some code path along the early interrupt handling is not I-pipe aware (un-hardened spinlock etc.). Did you already try enabling all I-pipe debug options? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
