On 2018-02-13 07:33, bharat gohil wrote: > Hi Jan, > > I took dump. pl. find attachment. > I don't know the side effect of printk, it not crashing but hangs after > "Activating hypervisor". I had try 4-5 time but it hangs everytime after > "Activating hypervisor"
That output looks good and consistent now. I suppose the lock-up is related to the long delay that the printing implies. You may filter out some uninteresting reports by adding "if (phys != 0x7c017000)" as condition (that address is - in your build - the zero page where the hypervisor regions gets mapped to for the root cell). Maybe there is some subtle issue related to the cores. You have a board with 2 A35 and 1 A72 cores, right? How about confining the startup tests on one of each core types for now? You could bring the cores of the other type offline (echo 0 > /sys/devices/system/cpu/cpuX/online), adjust the config to only contain the online cores, and retry. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to jailhouse-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
