[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Debugging Dom0 on OMAP5
On Sun, Oct 20, 2013 at 12:02 PM, Vaibhav Bedia <vaibhav.bedia@xxxxxxxxx> wrote: > Hi Ian, > > On Sun, Oct 20, 2013 at 11:42 AM, Ian Campbell <ian.campbell@xxxxxxxxxx> > wrote: >> On Sun, 2013-10-20 at 10:01 -0400, Vaibhav Bedia wrote: >>> MODULE[1]: 00000000a2000000 - 00000000a200b000 >>> MODULE[2]: 00000000a0000000 - 00000000a0a00000 >> >> You don't seem to have given dom0 any kind of command line. Try >> "console=hvc0". You have the Xen options, including the hvc console, >> enabled in your kernel I hope. >> > > I am trying to set xen,dom0-bootargs using the fdt command of U-Boot. > I did have to fight > the double quotes that fdt set was putting in but i managed to fix that. > > I did enable the various Xen options including the hvc console in the kernel. > > Just before invoking xen, here's what fdt list shows: > U-Boot# fdt list /chosen > chosen { > xen,dom0-bootargs = "console=hvc0,115200n8 vram=16M > root=/dev/ram initrd=0x83000000,16M ramdisk_size=65536 rw > earlyprintk=xen"; > xen,xen-bootargs = "dom0_mem=256M console=dtuart > dtuart=serial2 earlyprintk=xen"; > modules { > }; > }; > U-Boot# > > Does this look right? Argh... i should have not ignored the timer running @ 0Hz message for so long. With that fixed in DTB i can see Dom0 crash now. And somehow that change made the other Xen keyhandlers work again! _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |