[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Debugging Dom0 on OMAP5
On Thu, Oct 24, 2013 at 6:31 AM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote: > On Thu, 2013-10-24 at 06:17 -0400, Vaibhav Bedia wrote: >> Hi Ian, >> >> On Thu, Oct 24, 2013 at 4:18 AM, Ian Campbell <ian.campbell@xxxxxxxxxx> >> wrote: >> > On Wed, 2013-10-23 at 20:13 -0400, Vaibhav Bedia wrote: >> > >> >> Looking at the logs i noticed that the initrd is located outside the >> >> phys area that kernel >> >> is aware of and hence getting ignored. >> >> >> >> [...] >> >> [0.000000] INITRD: 0x83000000+0x01000000 is not a memory region - >> >> disabling initrd >> >> >> >> In the bootargs i have specified the initrd >> > >> > Do you mean the bootargs given to Xen or the ones given to dom0? How >> > exactly did you do this. >> > >> >> I specified that in the bootargs being passed to Dom0. >> U-Boot# fdt set /chosen xen,dom0-bootargs \"console=hvc0,115200n8 >> vram=16M root=/dev/ram initrd=0x83000000,16M ramdisk_size=65536 rw >> earlyprintk=xen lpj=61440 nohlt\" > > OK, this won't work.You've told dom0 that there is an initrd at > 0x83000000 but nothing here will actually be causing that to be the > case. > > You need to pass an initrd boot module to Xen, using the fdt based > protocol described in > http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/booting.txt;h=9802e5e20fd8c7da94eaa7b639b7530b951760eb;hb=HEAD > Xen will then take care of passing things to dom0. It works if i skip the initrd stuff in dom0-bootargs. I also got the filesystem on SD working now :) root@arm:~# uname -a Linux arm 3.12.0-rc5-00671-geb765a3-dirty #25 SMP Wed Oct 23 22:58:51 EDT 2013 armv7l GNU/Linux root@arm:~# cat /proc/interrupts CPU0 31: 295 GIC 31 events 39: 0 GIC 39 palmas 41: 0 GIC 41 l3-dbg-irq 42: 0 GIC 42 l3-app-irq 44: 3477 GIC 44 DMA 69: 5033 GIC 69 gp_timer 88: 1406 GIC 88 48070000.i2c 92: 0 GIC 92 4807c000.i2c 112: 13 GIC 112 4ae14000.wdt 115: 4659 GIC 115 mmc1 118: 421 GIC 118 mmc0 158: 2 GIC 158 talert 192: 0 xen-dyn-event xenbus 345: 0 GPIO 24 mmc1 449: 294 xen-percpu-virq hvc_console 451: 0 palmas 21 palmas_usb_id 453: 0 palmas 23 palmas_usb_vbus IPI0: 0 CPU wakeup interrupts IPI1: 0 Timer broadcast interrupts IPI2: 0 Rescheduling interrupts IPI3: 0 Function call interrupts IPI4: 0 Single function call interrupts IPI5: 0 CPU stop interrupts Err: 0 Now i need to figure out how to get a working domU. Thanks, Vaibhav _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |