[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [Renesas][Lager] Booting with XEN 4.6



On Wed, 2015-10-28 at 10:36 +0900, ììí wrote:
> Hello, Ferger.
> 
> Your advice is right to fix it.  I got message like below.

It would be super awesome if one or the other of you could update
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Lager with
the findings so far, if it isn't already mentioned (it seems like it might
be, but that edit by Max seems to predate this thread so I'm not sure if
something is missing).

Ian.

> .........................................................................
> ...................................
> 
> U-Boot 2014.10-00441-gf7ca1f7-dirty (Oct 22 2015 - 14:04:43)
> 
> CPU: Renesas Electronics R8A7790 rev 3.0
> Board: Lager
> I2C:   ready
> DRAM:  2 GiB
> SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB,
> total 64 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   sh_eth
> Hit any key to stop autoboot:  0 
> sh_eth Waiting for PHY auto negotiation to complete... done
> sh_eth: 100Base/Half
> Using sh_eth device
> TFTP from server 192.168.0.228; our IP address is 192.168.0.91
> Filename 'lager.dtb'.
> Load address: 0x70f00000
> Loading: ########
>          618.2 KiB/s
> done
> Bytes transferred = 36751 (8f8f hex)
> sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
> sh_eth Waiting for PHY auto negotiation to complete... done
> sh_eth: 100Base/Half
> Using sh_eth device
> TFTP from server 192.168.0.228; our IP address is 192.168.0.91
> Filename 'zImage-lager'.
> Load address: 0x72000000
> Loading:
> #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>         
>  #################################################################
>          ##################################################
>          698.2 KiB/s
> done
> Bytes transferred = 3580448 (36a220 hex)
> chosen {
>         bootargs = "root=/dev/ram rw earlyprintk rdinit=/sbin/init";
>         stdout-path = "/serial@e6e60000";
>         xen,xen-bootargs = "console=dtuart dom0_mem=1G";
>         xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug
> ignore_loglevel vmalloc=384M root=/dev/ram rw earlyprintk
> rdinit=/sbin/init";
>         modules {
>                 #address-cells = <0x00000001>;
>                 #size-cells = <0x00000001>;
>                 module@0x72000000 {
>                         reg = <0x72000000 0x0036a220>;
>                         compatible = "multiboot,kernel",
> "multiboot,module";
>                 };
>         };
> };
> sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
> sh_eth Waiting for PHY auto negotiation to complete... done
> sh_eth: 100Base/Half
> Using sh_eth device
> TFTP from server 192.168.0.228; our IP address is 192.168.0.91
> Filename 'xen-lager'.
> Load address: 0x70007fc0
> Loading:
> #################################################################
>         
>  #################################################################
>          ##################
>          712.9 KiB/s
> done
> Bytes transferred = 754608 (b83b0 hex)
> ## Booting kernel from Legacy Image at 70007fc0 ...
>    Image Name:   XEN
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    754544 Bytes = 736.9 KiB
>    Load Address: 90000000
>    Entry Point:  90000000
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 70f00000
>    Booting using the fdt blob at 0x70f00000
>    Loading Kernel Image ... OK
>    reserving fdt memory region: addr=70f00000 size=9000
>    Loading Device Tree to 407f4000, end 407fffff ... OK
> 
> Starting kernel ...
> 
> - UART enabled -
> - CPU 00000000 booting -
> - Xen starting in Hyp mode -
> - Zero BSS -
> - Setting up control registers -
> - Turning on paging -
> - Ready -
> (XEN) Checking for initrd in /chosen
> (XEN) RAM: 0000000040000000 - 000000007fffffff
> (XEN) RAM: 0000000140000000 - 00000001ffffffff
> (XEN) 
> (XEN) MODULE[0]: 00000000407f4000 - 00000000407fe000 Device Tree  
> (XEN) MODULE[1]: 0000000072000000 - 000000007236a220 Kernel       
> (XEN)  RESVD[0]: 0000000070f00000 - 0000000070f09000
> (XEN)  RESVD[1]: 000000007ff9a000 - 000000007ff9a120
> (XEN)  RESVD[2]: 00000000407f4000 - 00000000407fe000
> (XEN) 
> (XEN) Command line: console=dtuart dom0_mem=1G
> (XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000
> (XEN) Update BOOTMOD_XEN from 0000000090000000-0000000090101701 =>
> 000000007fc00000-000000007fd01701
> (XEN) Xen heap: 00000001f8000000-0000000200000000 (32768 pages)
> (XEN) Dom heap: 1015808 pages
> (XEN) Domain heap initialised
> (XEN) Platform: Renesas R-Car Gen2
> (XEN) Taking dtuart configuration from /chosen/stdout-path
> (XEN) Looking for dtuart at "/serial@e6e60000", options ""
>  Xen 4.6.0
> (XEN) Xen version 4.6.0 (charles@) (arm-linux-gnueabihf-gcc (Linaro GCC
> 4.9-2015.01-3) 4.9.3 20150113 (prerelease)) debug=y Wed Oct 28 10:29:39
> KS5
> (XEN) Latest ChangeSet: Mon Oct 5 15:33:39 2015 +0100 git:b24ad7b
> (XEN) Processor: 413fc0f2: "ARM Limited", variant: 0x3, part 0xc0f, rev
> 0x2
> (XEN) 32-bit Execution:
> (XEN)   Processor Features: 00001131:00011011
> (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
> (XEN)     Extensions: GenericTimer Security
> (XEN)   Debug Features: 02010555
> (XEN)   Auxiliary Features: 00000000
> (XEN)   Memory Model Features: 10201105 40000000 01240000 02102211
> (XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142
> 00000000
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 10000 KHz
> (XEN) GICv2 initialization:
> (XEN)         gic_dist_addr=00000000f1001000
> (XEN)         gic_cpu_addr=00000000f1002000
> (XEN)         gic_hyp_addr=00000000f1004000
> (XEN)         gic_vcpu_addr=00000000f1006000
> (XEN)         gic_maintenance_irq=25
> (XEN) GICv2: 416 lines, 8 cpus, secure (IID 0200043b).
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Allocated console ring of 64 KiB.
> (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
> (XEN) Bringing up CPU1
> (XEN) CPU1 never came online
> (XEN) Failed to bring up CPU 1 (error -5)
> (XEN) Bringing up CPU2
> (XEN) CPU2 never came online
> (XEN) Failed to bring up CPU 2 (error -5)
> (XEN) Bringing up CPU3
> (XEN) CPU3 never came online
> (XEN) Failed to bring up CPU 3 (error -5)
> (XEN) Bringing up CPU4
> (XEN) CPU4 never came online
> (XEN) Failed to bring up CPU 4 (error -5)
> (XEN) Bringing up CPU5
> (XEN) CPU5 never came online
> (XEN) Failed to bring up CPU 5 (error -5)
> (XEN) Bringing up CPU6
> (XEN) CPU6 never came online
> (XEN) Failed to bring up CPU 6 (error -5)
> (XEN) Bringing up CPU7
> (XEN) CPU7 never came online
> (XEN) Failed to bring up CPU 7 (error -5)
> (XEN) Brought up 1 CPUs
> (XEN) P2M: 40-bit IPA
> (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
> (XEN) I/O virtualisation disabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading kernel from boot module @ 0000000072000000
> (XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
> (XEN) BANK[0] 0x00000048000000-0x00000070000000 (640MB)
> (XEN) BANK[1] 0x000001d8000000-0x000001f0000000 (384MB)
> (XEN) Grant table range: 0x0000007fc00000-0x0000007fc61000
> (XEN) Loading zImage from 0000000072000000 to 000000004fc00000
> -000000004ff6a220
> (XEN) Allocating PPI 16 for event channel interrupt
> (XEN) Loading dom0 DTB to 0x0000000050000000-0x0000000050008b0d
> (XEN) Scrubbing Free RAM on 1 nodes using 1 CPUs
> (XEN) ................................done.
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
> to Xen)
> (XEN) Freed 264kB init memory.
> (XEN) do_physdev_op 16 cmd=25: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> (XEN) do_physdev_op 16 cmd=15: not implemented yet
> Booting Linux on physical CPU 0x0
> Linux version 3.19.8 (charles@charles-desktop) (gcc version 4.9.3
> 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #2 Mon Oct 26 14:47:40
> KST 205
> CPU: ARMv7 Processor [413fc0f2] revision 2 (ARMv7), cr=10c53c7d
> CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
> Machine model: Lager
> Ignoring memory block 0x1d8000000 - 0x1f0000000
> debug: ignoring loglevel setting.
> Truncating RAM at 0x48000000-0x70000000 to -0x6f000000
> Memory policy: Data cache writeback
> On node 0 totalpages: 159744
> free_area_init_node: node 0, pgdat c05fa2a0, node_mem_map e6b1a000
>   Normal zone: 1248 pages used for memmap
>   Normal zone: 0 pages reserved
>   Normal zone: 159744 pages, LIFO batch:31
> psci: probing for conduit method from DT.
> psci: PSCIv0.2 detected in firmware.
> psci: Using standard PSCI v0.2 function IDs
> CPU: All CPU(s) started in SVC mode.
> pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> pcpu-alloc: [0] 0 
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> 158496
> Kernel command line: console=hvc0 earlyprintk=xen debug ignore_loglevel
> vmalloc=384M root=/dev/ram rw earlyprintk rdinit=/sbin/init
> PID hash table entries: 4096 (order: 2, 16384 bytes)
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Memory: 626732K/638976K available (3740K kernel code, 170K rwdata, 932K
> rodata, 1240K init, 160K bss, 12244K reserved, 0K cma-reserved)
> Virtual kernel memory layout:
>     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
>     vmalloc : 0xe7800000 - 0xff000000   ( 376 MB)
>     lowmem  : 0xc0000000 - 0xe7000000   ( 624 MB)
>       .text : 0xc0008000 - 0xc049903c   (4677 kB)
>       .init : 0xc049a000 - 0xc05d0000   (1240 kB)
>       .data : 0xc05d0000 - 0xc05fabe0   ( 171 kB)
>        .bss : 0xc05fabe0 - 0xc0622c58   ( 161 kB)
> NR_IRQS:16 nr_irqs:16 16
> sched_clock: 32 bits at 128 Hz, resolution 7812500ns, wraps every
> 16777216000000000ns
> Console: colour dummy device 80x30
> Calibrating delay loop (skipped) preset value.. 1300.08 BogoMIPS
> (lpj=5078125)
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
> CPU: Testing write buffer coherency: ok
> irq: no irq domain found for /interrupt-controller !
> Xen 4.6 support found, events_irq=0 gnttab_frame=0x7fc00000
> xen:grant_table: Grant tables using version 1 layout
> Grant table initialized
> xen:events: Using FIFO-based ABI
> Error request IRQ 0
> Setting up static identity map for 0x483adb68 - 0x483adbc0
> devtmpfs: initialized
> VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
> pinctrl core: initialized pinctrl subsystem
> NET: Registered protocol family 16
> DMA: preallocated 256 KiB pool for atomic coherent allocations
> xen:swiotlb_xen: Warning: only able to allocate 16 MB for software IO TLB
> software IO TLB [mem 0x6b000000-0x6c000000] (16MB) mapped at [e3000000
> -e3ffffff]
> sh-pfc pfc-r8a7790: r8a77900_pfc support registered
> renesas_irqc renesas_irqc.0: driving 4 irqs
> No ATAGs?
> hw-breakpoint: Failed to enable monitor mode on CPU 0.
> xen:balloon: Initialising balloon driver
> xen_balloon: Initialising balloon driver
> SDHI0Vcc: Failed to request enable GPIO184: -517
> reg-fixed-voltage reg-fixed-voltage.1: Failed to register regulator: -517
> platform reg-fixed-voltage.1: Driver reg-fixed-voltage requests probe
> deferral
> SDHI2Vcc: Failed to request enable GPIO185: -517
> reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -517
> platform reg-fixed-voltage.2: Driver reg-fixed-voltage requests probe
> deferral
> gpio-regulator gpio-regulator.0: Could not obtain regulator setting
> GPIOs: -517
> platform gpio-regulator.0: Driver gpio-regulator requests probe deferral
> gpio-regulator gpio-regulator.1: Could not obtain regulator setting
> GPIOs: -517
> platform gpio-regulator.1: Driver gpio-regulator requests probe deferral
> vgaarb: loaded
> SCSI subsystem initialized
> libata version 3.00 loaded.
> Linux video capture interface: v2.00
> sh_cmt sh-cmt-48-gen2.0: ch0: used for clock events
> sh_cmt sh-cmt-48-gen2.0: ch0: used for periodic clock events
> sh_cmt sh-cmt-48-gen2.0: ch1: used as clock source
> Advanced Linux Sound Architecture Driver Initialized.
> Switched to clocksource sh-cmt-48-gen2.0
> sh_cmt sh-cmt-48-gen2.0: ch0: used for oneshot clock events
> NET: Registered protocol family 2
> TCP established hash table entries: 8192 (order: 3, 32768 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP: reno registered
> UDP hash table entries: 512 (order: 1, 8192 bytes)
> UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
> NET: Registered protocol family 1
> RPC: Registered named UNIX socket transport module.
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> RPC: Registered tcp NFSv4.1 backchannel transport module.
> PCI: CLS 0 bytes, default 64
> futex hash table entries: 256 (order: -1, 3072 bytes)
> NFS: Registering the id_resolver key type
> Key type id_resolver registered
> Key type id_legacy registered
> nfs4filelayout_init: NFSv4 File Layout Driver Registering...
> io scheduler noop registered (default)
> gpio_rcar gpio_rcar.0: driving 32 GPIOs
> gpio_rcar gpio_rcar.1: driving 32 GPIOs
> gpio_rcar gpio_rcar.2: driving 32 GPIOs
> gpio_rcar gpio_rcar.3: driving 32 GPIOs
> gpio_rcar gpio_rcar.4: driving 32 GPIOs
> gpio_rcar gpio_rcar.5: driving 32 GPIOs
> pci-rcar-gen2 pci-rcar-gen2.1: PCI: bus0 revision 11
> pci-rcar-gen2 pci-rcar-gen2.1: PCI host bridge to bus 0000:01
> pci_bus 0000:01: root bus resource [io  0xee0a0000-0xee0affff]
> pci_bus 0000:01: root bus resource [mem 0xee0a0000-0xee0affff]
> pci_bus 0000:01: No busn resource found for root bus, will use [bus 01
> -ff]
> pci 0000:01:00.0: [1033:0000] type 00 class 0x060000
> pci 0000:01:00.0: reg 0x10: [mem 0xee0b0800-0xee0b0bff]
> pci 0000:01:00.0: reg 0x14: [mem 0x40000000-0x7fffffff pref]
> pci 0000:01:00.0: Failed to add - passthrough or MSI/MSI-X might fail!
> pci 0000:01:01.0: [1033:0035] type 00 class 0x0c0310
> pci 0000:01:01.0: reg 0x10: [mem 0x00000000-0x00000fff]
> pci 0000:01:01.0: supports D1 D2
> pci 0000:01:01.0: PME# supported from D0 D1 D2 D3hot
> pci 0000:01:01.0: Failed to add - passthrough or MSI/MSI-X might fail!
> pci 0000:01:02.0: [1033:00e0] type 00 class 0x0c0320
> pci 0000:01:02.0: reg 0x10: [mem 0x00000000-0x000000ff]
> pci 0000:01:02.0: supports D1 D2
> pci 0000:01:02.0: PME# supported from D0 D1 D2 D3hot
> pci 0000:01:02.0: Failed to add - passthrough or MSI/MSI-X might fail!
> PCI: bus1: Fast back to back transfers disabled
> pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
> pci 0000:01:01.0: can't enable device: BAR 0 [mem 0x00000000-0x00000fff]
> not claimed
> pci 0000:01:01.0: Can't enable PCI device, BIOS handoff failed.
> pci 0000:01:02.0: can't enable device: BAR 0 [mem 0x00000000-0x000000ff]
> not claimed
> pci 0000:01:02.0: Can't enable PCI device, BIOS handoff failed.
> pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:01:01.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:01:02.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:01:01.0: BAR 0: assigned [mem 0xee0a0000-0xee0a0fff]
> pci 0000:01:02.0: BAR 0: assigned [mem 0xee0a1000-0xee0a10ff]
> pci-rcar-gen2 pci-rcar-gen2.2: PCI: bus0 revision 11
> pci-rcar-gen2 pci-rcar-gen2.2: PCI host bridge to bus 0000:02
> pci_bus 0000:02: root bus resource [io  0xee0c0000-0xee0cffff]
> pci_bus 0000:02: root bus resource [mem 0xee0c0000-0xee0cffff]
> pci_bus 0000:02: No busn resource found for root bus, will use [bus 02
> -ff]
> pci 0000:02:00.0: [1033:0000] type 00 class 0x060000
> pci 0000:02:00.0: reg 0x10: [mem 0xee0d0800-0xee0d0bff]
> pci 0000:02:00.0: reg 0x14: [mem 0x40000000-0x7fffffff pref]
> pci 0000:02:00.0: Failed to add - passthrough or MSI/MSI-X might fail!
> pci 0000:02:01.0: [1033:0035] type 00 class 0x0c0310
> pci 0000:02:01.0: reg 0x10: [mem 0x00000000-0x00000fff]
> pci 0000:02:01.0: supports D1 D2
> pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot
> pci 0000:02:01.0: Failed to add - passthrough or MSI/MSI-X might fail!
> pci 0000:02:02.0: [1033:00e0] type 00 class 0x0c0320
> pci 0000:02:02.0: reg 0x10: [mem 0x00000000-0x000000ff]
> pci 0000:02:02.0: supports D1 D2
> pci 0000:02:02.0: PME# supported from D0 D1 D2 D3hot
> pci 0000:02:02.0: Failed to add - passthrough or MSI/MSI-X might fail!
> PCI: bus2: Fast back to back transfers disabled
> pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
> pci 0000:02:01.0: can't enable device: BAR 0 [mem 0x00000000-0x00000fff]
> not claimed
> pci 0000:02:01.0: Can't enable PCI device, BIOS handoff failed.
> pci 0000:02:02.0: can't enable device: BAR 0 [mem 0x00000000-0x000000ff]
> not claimed
> pci 0000:02:02.0: Can't enable PCI device, BIOS handoff failed.
> pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:01:01.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:01:02.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:02:00.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:02:01.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:02:02.0: of_irq_parse_pci() failed with rc=-22
> pci 0000:02:01.0: BAR 0: assigned [mem 0xee0c0000-0xee0c0fff]
> pci 0000:02:02.0: BAR 0: assigned [mem 0xee0c1000-0xee0c10ff]
> xen:xen_evtchn: Event-channel device installed
> console [hvc0] enabled
> SuperH (H)SCI(F) driver initialized
> sh-sci.0: ttySC0 at MMIO 0xe6c40000 (irq = 176, base_baud = 0) is a scifa
> sh-sci.1: ttySC1 at MMIO 0xe6c50000 (irq = 177, base_baud = 0) is a scifa
> sh-sci.2: ttySC2 at MMIO 0xe6c20000 (irq = 180, base_baud = 0) is a scifb
> sh-sci.3: ttySC3 at MMIO 0xe6c30000 (irq = 181, base_baud = 0) is a scifb
> sh-sci.4: ttySC4 at MMIO 0xe6ce0000 (irq = 182, base_baud = 0) is a scifb
> sh-sci.5: ttySC5 at MMIO 0xe6c60000 (irq = 183, base_baud = 0) is a scifa
> sh-sci.6: ttySC6 at MMIO 0xe6e60000 (irq = 184, base_baud = 0) is a scif
> sh-sci.7: ttySC7 at MMIO 0xe6e68000 (irq = 185, base_baud = 0) is a scif
> sh-sci.8: ttySC8 at MMIO 0xe62c0000 (irq = 186, base_baud = 0) is a hscif
> sh-sci.9: ttySC9 at MMIO 0xe62c8000 (irq = 187, base_baud = 0) is a hscif
> [drm] Initialized drm 1.1.0 20060810
> scsi host0: sata_rcar
> ata1: SATA max UDMA/133 irq 138
> m25p80 spi0.0: s25fl512s (65536 Kbytes)
> Creating 3 MTD partitions on "m25p80":
> 0x000000000000-0x000000040000 : "loader"
> 0x000000040000-0x000000440000 : "user"
> 0x000000440000-0x000004000000 : "flash"
> renesas_spi qspi.0: probed
> libphy: sh_mii: probed
> sh-eth r8a7790-ether eth0: Base address at 0xee700000, 2e:09:0a:00:6d:c9,
> IRQ 194.
> xen_netfront: Initialising Xen virtual ethernet driver
> mousedev: PS/2 mouse device common for all mice
> i2c-rcar i2c-rcar_gen2.0: probed
> i2c-rcar i2c-rcar_gen2.1: probed
> i2c-rcar i2c-rcar_gen2.2: probed
> i2c-rcar i2c-rcar_gen2.3: probed
> soc-camera-pdrv soc-camera-pdrv.1: Probing soc-camera-pdrv.1
> adv7180 2-0020: chip found @ 0x20 (i2c-rcar_gen2)
> rcar_thermal rcar_thermal: 1 sensor probed
> Driver 'mmcblk' needs updating - please use bus_type methods
> sh_mobile_sdhi sh_mobile_sdhi.0: No vmmc regulator found
> sh_mobile_sdhi sh_mobile_sdhi.0: No vqmmc regulator found
> platform sh_mobile_sdhi.0: Driver sh_mobile_sdhi requests probe deferral
> sh_mobile_sdhi sh_mobile_sdhi.2: No vmmc regulator found
> sh_mobile_sdhi sh_mobile_sdhi.2: No vqmmc regulator found
> platform sh_mobile_sdhi.2: Driver sh_mobile_sdhi requests probe deferral
> sh_mmcif sh_mmcif.1: No vqmmc regulator found
> sh_mmcif sh_mmcif.1: Chip version 0x0003, clock rate 12MHz
> ata1: link resume succeeded after 1 retries
> asoc-simple-card asoc-simple-card: ASoC: CPU DAI rcar_sound not
> registered
> platform asoc-simple-card: Driver asoc-simple-card requests probe
> deferral
> rcar_sound rcar_sound: probed
> TCP: cubic registered
> NET: Registered protocol family 17
> bridge: automatic filtering via arp/ip/ip6tables has been deprecated.
> Update your scripts to load br_netfilter if you need this.
> Key type dns_resolver registered
> ata1: SATA link down (SStatus 0 SControl 300)
> sh_mmcif sh_mmcif.1:  CRC error: state 1, wait 1
> mmc0: BKOPS_EN bit is not set
> mmc0: new high speed MMC card at address 0001
> mmcblk0: mmc0:0001 eMMC   7.28 GiB 
> mmcblk0boot0: mmc0:0001 eMMC   partition 1 4.00 MiB
> mmcblk0boot1: mmc0:0001 eMMC   partition 2 4.00 MiB
>  mmcblk0: p1
> sh_mobile_sdhi sh_mobile_sdhi.0: mmc1 base at 0xee100000 clock rate 97
> MHz
> sh_mobile_sdhi sh_mobile_sdhi.2: mmc2 base at 0xee140000 clock rate 48
> MHz
> asoc-simple-card asoc-simple-card: ak4642-hifi <-> rcar_sound mapping ok
> input: gpio-keys as /devices/platform/gpio-keys/input/input0
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> 
> .........................................................................
> ...................................
> 
> As you know, I still have problem to wake up CPUs(1~7) and to login DOM0
> and looking for the way to fix it.
> 
> Thanks.
> 
> 
> 2015-10-26 18:11 GMT+09:00 Ferger, Max <M.Ferger@xxxxxxxxxx>:
> > Hello!
> > 
> > > From: xen-users-bounces@xxxxxxxxxxxxx [mailto:
> > xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of ???
> > > Sent: Monday, October 26, 2015 3:54 AM
> > > To: xen-users@xxxxxxxxxxxxx
> > > Subject: [Xen-users] [Renesas][Lager] Booting with XEN 4.6
> > >
> > > I have problem on the step of booting with xen with the reference
> > site
> > > (
> > http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Lager).
> > 
> > Maybe, youâd like to read about the mostly similar problems I had
> > and about some that could be solved with Renesasâ Lager board ?
> > http://lists.xen.org/archives/html/xen-devel/2015-10/msg01718.html
> > 
> > > I have used the environment like below.
> > >
> > > - xen version : xen4.6 Release version
> > > - linux kernel : mainline 3.19.8 with DTS(r8a7790-lager.dts)
> > > - Without using XSM module ( I got error message for compiling XSM
> > > module on ubuntu14.04 host, if any got how to compile let me know)
> > 
> > My Linux Mint 17 didn't complain, but it is based on a similar Ubuntu.
> > 
> > > I had tried  to setup board and started,and then got
> > > below message that did not bring up CPU1 ~ 7.
> > > Lager board got brought up CPU0 only.
> > > .....@3rd problem Got errors on bring up CPSs  ...................
> > 
> > My Lager board doesn't boot CPU1 t/m CPU7 neither, so far.
> > 
> > It was possible for me to see Dom0 messages, still no login.
> > 
> > > Also did not get problem for the console.
> > > .....@2nd problem Got errors on uart from the chosen node of original
> >   DTB  ...................
> > > (XEN) Taking dtuart configuration from /chosen/stdout-path
> > > (XEN) Looking for dtuart at "/serial@e6c40000", options ""
> > > (XEN) Unable to initialize dtuart: -9
> > > (XEN) Bad console= option 'dtuart'
> > 
> > I got a similar message.  Please integrate the device tree (DT)
> > changes I added to the /Lager wiki last week!
> > 
> > You can find out, whether they are applied via 'fdt' command in U-Boot:
> > 
> > fdt print /chosen
> > 
> > Should give:
> > ----- 8< -----
> > chosen {
> >         bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
> >         stdout-path = "/serial@e6e60000";
> >         xen,xen-bootargs = "console=dtuart dom0_mem=1G";
> >         xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug
> > ignore_loglevel vmalloc=384M video=HDMI-A-1:1920x1080-32@60 ip=192.168.
> > 0.5:192.168.0.15:192.168.0.15:255.255.255.0:lager:eth0::: root=/dev/nfs
> > rw nfsroot=192.168.0.15:/nfsroot rootdelay clk_ignore_unused";
> >         modules {
> >                 #address-cells = <0x00000001>;
> >                 #size-cells = <0x00000001>;
> >                 module@0x72000000 {
> >                         reg = <0x72000000 0x002fcca0>;
> >                         compatible = "multiboot,kernel",
> > "multiboot,module";
> >                 };
> >                 module@0x74000000 {
> >                         reg = <0x74000000 0x00002559>;
> >                         compatible = "xen,xsm-policy",
> > "multiboot,module";
> >                 };
> >         };
> > };
> > ----- 8< -----
> > 
> > 
> > > .....@4th problem Got errors on create DOM0 kernel 
> > ...................
> > > (XEN) *** LOADING DOMAIN 0 ***
> > > (XEN) Loading kernel from boot module @ 0000000060000000
> > > (XEN) Allocating 1:1 mappings totalling 128MB for dom0:
> > > (XEN) BANK[0] 0x00000068000000-0x00000070000000 (128MB)
> > > (XEN) Grant table range: 0x0000007fc00000-0x0000007fc61000
> > > (XEN) DT: no ranges; cannot enumerate
> > > (XEN) Device tree generation failed (-22).
> > 
> > This is fixable by DTS addition:
> > ----- 8< -----
> > {
> >         /* add required 'ranges;' to all PCI devices */
> >         pci0: pci@ee090000 {
> >                 usb@0,1 {
> >                         #address-cells = <3>;
> >                         #size-cells = <2>;
> >                         ranges;
> >                 };
> >                 usb@0,2 {
> >                         #address-cells = <3>;
> >                         #size-cells = <2>;
> >                         ranges;
> >                 };
> >         };
> >         pci2: pci@ee0d0000 {
> >                 usb@0,1 {
> >                         #address-cells = <3>;
> >                         #size-cells = <2>;
> >                         ranges;
> >                 };
> >                 usb@0,2 {
> >                         #address-cells = <3>;
> >                         #size-cells = <2>;
> >                         ranges;
> >                 };
> >         };
> > };
> > ----- 8< -----
> > 
> > Good luck and please get me updated on further progres!
> > 
> > Max Ferger
> > m.ferger@xxxxxxxxxx
> > 
> > 
> > 
> > Leopold KOSTAL GmbH & Co. KG - Sitz LÃdenscheid, Registergericht
> > Iserlohn HRA 2854, phG Kostal Verwaltungsgesellschaft mbH,
> > Registergericht Iserlohn HRB 4061 - USt-Id-Nr./Vat No.: DE 125800885
> > Post- und Werksanschrift: An der Bellmerei 10, D-58513 LÃdenscheid *
> > Telefon: +49 2351 16-0 * Telefax: +49 2351 16-2400 Bellmerei
> > GeschÃftsfÃhrung: Dipl.-Oec. Andreas Kostal (Vorsitzender), Dipl.-Kfm.
> > Helmut Kostal, Dipl.-Ing. Marwin Kinzl, Dr.-Ing. Ludger Laufenberg,
> > Dipl.-Kfm. Ulrich Zimmermann
> > 
> > 
> 
> 
> -- 
> Happy Virus....
> ì ìí 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.