Dear Moinuddin, What changes have to you done in device tree for Dom0?
I'm curious with few moments: 1. (XEN) omap-uart: Unable to retrieve the IRQ (XEN) Unable to initialize dtuart: -22 (XEN) Bad console= option 'dtuart' Looks there is some problems with uart node. 2. Strange kernel command line: Kernel command line: console=ttyS0,115200 earlyprintk omapdrm.num_crtc=2 root=/dev/mmcblk0p2 rw rootwait rootfstype=ext4 init=/init drm. rnodes=1 androidboot.selinux=permissive snd.slots_reserved=1,1 snd-soc-core.pmdown_time=-1 uio_pdrv_genirq.of_id=generic-uio androidboot.console=ttyS0 androidboot.hardware=jacinto6evmboard Looks like it mixed: android & linux at some time. Are you trying to run Android as dom0? And if you are using xen, you don't have to specify console for dom0. 3. [ 0.831911] palmas 0-0058: IRQ missing: skipping irq request [ 5.048233] omap_i2c 4807a000.i2c: failure requesting irq 328 Looks like there is some problems with interrupt mapping. Xen doesn't forward interrupts with number bigger than 192. If you need to forward such IRQ, you have to use crossbar - it can be statically configured during u-boot stage. But at the same time - you have to update Dom0 device tree - to use gic as main interrupt controller, not crossbar. 4. [ 5.436504] omapdss_dss 58000000.dss: master bind failed: -517 - looks like same problem, please look through the log & fix in the same way as 4th. 5. [ 6.881378] Waiting for root device /dev/mmcblk0p2... Boot log shows, that your partition list are not enumerated - this might be the same problem - some problems for emmc/sd card IRQ. In general it looks like you use wrong device tree. Please, look into [1] as reference to update your device tree. [1] https://wiki.xenproject.org/wiki/User:Xen_intruction_setup_for_dra7xx-evm_board With the best regards, Iurii Mykhalskyi On Tue, Feb 27, 2018 at 11:09 AM, moin anjnawala <[email protected]> wrote: > Hi, > > I am trying to boot kernel 4.4 on Jacinto-6 EVM board, I am facing error > from xen. Please find attached log to find errors. > > The kernel is stuck at > [ 6.881378] Waiting for root device /dev/mmcblk0p2... > > Is it due to i2c related errors in boot log as mentioned below? > [ 0.831911] palmas 0-0058: IRQ missing: skipping irq request > [ 1.860292] omap_i2c 48070000.i2c: controller timed out > [ 1.880663] palmas: probe of 0-0058 failed with error -110 > [ 2.902874] omap_i2c 48070000.i2c: controller timed out > [ 2.922933] pcf857x: probe of 0-0020 failed with error -110 > [ 3.945557] omap_i2c 48070000.i2c: controller timed out > [ 3.965619] pcf857x: probe of 0-0021 failed with error -110 > [ 3.971774] omap_i2c 48070000.i2c: bus 0 rev0.12 at 400 kHz > [ 5.000328] omap_i2c 48072000.i2c: controller timed out > [ 5.020390] pcf857x: probe of 1-0026 failed with error -110 > [ 5.026750] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz > [ 5.033041] omap_i2c 48060000.i2c: bus 2 rev0.12 at 400 kHz > [ 5.039104] genirq: Flags mismatch irq 328. 00006000 (4807a000.i2c) vs. > 00006000 (48072000.i2c) > [ 5.048233] omap_i2c 4807a000.i2c: failure requesting irq 328 > [ 5.054274] omap_i2c: probe of 4807a000.i2c failed with error -16 > > Can anyone provide the solution to these problems? > > Thanks, > Moinuddin > > > > _______________________________________________ > Xen-devel mailing list > [email protected] > https://lists.xenproject.org/mailman/listinfo/xen-devel > -- Iurii Mykhalskyi | Lead Software Engineer GlobalLogic P +38.044.492.9695x3664 M +38.096.311.5467 S mad-nemoi www.globallogic.com <http://www.globallogic.com/> http://www.globallogic.com/email_disclaimer.txt
_______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
