All of lore.kernel.org
 help / color / mirror / Atom feed
From: George John <georgeeldhojohn@gmail.com>
To: Andrii Anisov <andrii.anisov@gmail.com>
Cc: xen-devel@lists.xenproject.org, Julien Grall <julien.grall@arm.com>
Subject: Re: Error regarding filesystem in Dom0 in lager board
Date: Tue, 22 Nov 2016 23:10:55 +0530	[thread overview]
Message-ID: <CANou6Srkzb83kerTRnpZ_c50cRkzqf9pishnLzpdM77V==vx0w@mail.gmail.com> (raw)
In-Reply-To: <CAC1WxdgkqPv2e4f6ZCObQojzT+vBuaBjUQUWs-JvNnyaLGrEFA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3338 bytes --]

Thank you all,

what Andrii suggested was really the problem. I modified the uart driver in
the kernel, so that it won't disable the port the xen was using(scif0). Now
the linux Dom0 was booted up. But the new problem now occured was that
filesystem getting stuck before login prompt. I assume it was the problem
when the serial getty service tries to use the scif0 port the xen was using.
Can any one suggest me a solution.?. I am attaching the log

Thanks and regards,

George

On Mon, Nov 21, 2016 at 4:45 PM, Andrii Anisov <andrii.anisov@gmail.com>
wrote:

> John,
>
> I guess you should remove descriptions of clocks and pins of a serial
> port owned by XEN from the DTSI.
> Normally kernel decides that they are not used, so disables them and
> you think your system hangs.
> I'm not really sure why you are reached this far (rootfs mounting), it
> should be "hanged" earlier. But it could be you case.
>
> Sincerely,
> Andrii Anisov.
>
>
> On Sun, Nov 20, 2016 at 5:44 PM, George John <georgeeldhojohn@gmail.com>
> wrote:
> > Hi,
> >
> >
> > On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall <julien.grall@arm.com>
> wrote:
> >>
> >>
> >>
> >> On 16/11/2016 11:23, George John wrote:
> >>>
> >>> Hi,
> >>
> >>
> >> Hello George,
> >>
> >>> I just bumped in to some errors related to filesystem . The following
> is
> >>> the log. I am using xen 4.7.1 along with linux kernel 3.19.8 as Dom0
> >>
> >>
> >> [...]
> >>
> >>> sh_mobile_sdhi sh_mobile_sdhi.0: mmc1 base at 0xee100000 clock rate 97
> >>> MHz
> >>> ata1: link resume succeeded after 1 retries
> >>> ata1: SATA link down (SStatus 0 SControl 300)
> >>> 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
> >>> �H�EXT4-fs (mmcblk0p1): error count since last fsck: 24
> >>> EXT4-fs (mmcblk0p1): initial error at time 11: mb_free_blocks:1450:
> >>> inode 67523: block 296960
> >>> EXT4-fs (mmcblk0p1): last error at time 10: ext4_free_inode:340
> >>
> >>
> >> It looks like the filesystem is corrupted. Have you tried to verify the
> >> filesystem with fsck?
> >
> >
> > No, I haven't verified the filesystem. But the filesystem is working
> with no
> > problems for native linux. Also Network file system( working with native
> > linux) is not working when linux is running above xen. So I assumed it
> may
> > be the problem with accessibility of hardware by linux when running above
> > the hypervisor.
> >
> >>>
> >>>
> >>> After this the system hangs
> >>
> >>
> >> Do you mean that even Xen is becoming inaccessible?
> >>
> >> You can try to switch to the Xen console by type 3-times "CTRL-a". You
> >> should see a message from Xen telling you it has switched to Xen. If it
> >> works, then only DOM0 is hanging.
> >
> >
> > Yes, I have tried that. Xen is also becoming inaccessible. Nothing works
> > after the system hang.
> >
> >>
> >>
> >> Regards,
> >>
> >> --
> >> Julien Grall
> >
> >
> >
> > Regards,
> > George
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > https://lists.xen.org/xen-devel
> >
>

[-- Attachment #1.2: Type: text/html, Size: 4660 bytes --]

[-- Attachment #2: log_22-11-2016 --]
[-- Type: application/octet-stream, Size: 27349 bytes --]

----------------------------------------------------------
| LAGER SPI_BOOT_LOADER (USER:S25FL512) V0.12 2013.04.09 |
|        -----   QUAD READ (DMA Version)   -----         |
----------------------------------------------------------
 Now Loading ....... com

U-Boot 2014.10 (Nov 03 2016 - 17:24:44)

CPU: Renesas Electronics R8A7790 rev 1.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.1; our IP address is 192.168.0.20
Filename 'xen-uImage'.
Load address: 0x70007fc0
Loading: #################################################################
	 #################################################################
	 ########################
	 2.8 MiB/s
done
Bytes transferred = 787392 (c03c0 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.1; our IP address is 192.168.0.20
Filename 'uImage-r8a7790-lager-xen.dtb'.
Load address: 0x70f00000
Loading: ########
	 1.6 MiB/s
done
Bytes transferred = 36467 (8e73 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.1; our IP address is 192.168.0.20
Filename 'zImage-uImage'.
Load address: 0x72000000
Loading: #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ############################################################
	 2.6 MiB/s
done
Bytes transferred = 2635024 (283510 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.1; our IP address is 192.168.0.20
Filename 'xenpolicy-4.7.1'.
Load address: 0x74000000
Loading: ##
	 878.9 KiB/s
done
Bytes transferred = 9906 (26b2 hex)
## Booting kernel from Legacy Image at 70007fc0 ...
   Image Name:   XEN
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    787328 Bytes = 768.9 KiB
   Load Address: 90000000
   Entry Point:  90000000
## Flattened Device Tree blob at 70f00000
   Booting using the fdt blob at 0x70f00000
   Loading Kernel Image ... OK
   Loading Device Tree to 40ef4000, end 40effe72 ... 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]: 0000000040ef4000 - 0000000040efd000 Device Tree  
(XEN) MODULE[1]: 0000000072000000 - 0000000072302518 Kernel       
(XEN) MODULE[2]: 0000000074000000 - 00000000740026b2 XSM          
(XEN)  RESVD[0]: 000000007ff9a000 - 000000007ff9a120
(XEN)  RESVD[1]: 0000000040ef4000 - 0000000040efd000
(XEN) 
(XEN) Command line: console=dtuart dom0_mem=1G
(XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000
(XEN) Update BOOTMOD_XEN from 0000000090000000-0000000090105781 => 000000007fc00000-000000007fd05781
(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.7.1
(XEN) Xen version 4.7.1 (teltvm@tvm.telxsi.com) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) 4.8.4) debug=y Tue Nov 22 11:39:54 IST 2016
(XEN) Latest ChangeSet: 
(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: WARNING: The GICC size is too small: 0x1000 expected 0x2000
(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 32 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000002 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000003 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Brought up 4 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-0x0000007fc64000
(XEN) Loading zImage from 0000000072000000 to 000000004fc00000-000000004fe83510
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000050000000-0x0000000050008c1d
(XEN) Scrubbing Free RAM on 1 nodes using 4 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 276kB init memory.
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=25: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
(XEN) physdev.c:17:d0v0 PHYSDEVOP cmd=15: not implemented
Booting Linux on physical CPU 0x0
Linux version 3.19.8 (teltvm@teltvm2038x) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #75 Tue Nov 22 17:19:03 IST 2016
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
Truncating RAM at 0x48000000-0x70000000 to -0x6f000000
Memory policy: Data cache writeback
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at arch/arm/kernel/devtree.c:144 arm_dt_init_cpu_maps+0xc0/0x12c()
DT /cpu 2 nodes greater than max cores 1, capping them
CPU: 0 PID: 0 Comm: swapper Not tainted 3.19.8 #75
Hardware name: lager
Backtrace: 
[<c00121f4>] (dump_backtrace) from [<c0012388>] (show_stack+0x18/0x1c)
 r6:c04899bf r5:00000009 r4:00000000 r3:00200000
[<c0012370>] (show_stack) from [<c03dcfe4>] (dump_stack+0x20/0x28)
[<c03dcfc4>] (dump_stack) from [<c0022ba4>] (warn_slowpath_common+0x88/0xb0)
[<c0022b1c>] (warn_slowpath_common) from [<c0022c38>] (warn_slowpath_fmt+0x38/0x40)
 r8:c0514028 r7:e6b1785c r6:00000001 r5:00000000 r4:e6b17ac4
[<c0022c04>] (warn_slowpath_fmt) from [<c04d9370>] (arm_dt_init_cpu_maps+0xc0/0x12c)
 r3:00000002 r2:c0489a02
[<c04d92b0>] (arm_dt_init_cpu_maps) from [<c04d8964>] (setup_arch+0x5e0/0x78c)
 r7:c050b708 r6:c0543598 r5:c04f5fcc r4:e6ffcf80
[<c04d8384>] (setup_arch) from [<c04d69c4>] (start_kernel+0x80/0x33c)
 r10:00000000 r9:c0508000 r8:48004059 r7:ffffffff r6:c052b100 r5:00000001
 r4:00000000
[<c04d6944>] (start_kernel) from [<48008070>] (0x48008070)
 r10:00000000 r9:413fc0f2 r8:48004059 r7:c050b810 r6:c04f7328 r5:c0508078
 r4:c052bb94
---[ end trace cb88537fdc8fa200 ]---
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.
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 158496
Kernel command line: console=hvc0  vmalloc=384M video=HDMI-A-1:1920x1080-32@60 root=/dev/mmcblk1p1 rw rootfstype=ext2 rootwait
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: 627556K/638976K available (3944K kernel code, 172K rwdata, 968K rodata, 168K init, 165K bss, 11420K 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 - 0xc04d5034   (4917 kB)
      .init : 0xc04d6000 - 0xc0500000   ( 168 kB)
      .data : 0xc0500000 - 0xc052b100   ( 173 kB)
       .bss : 0xc052b100 - 0xc05547b8   ( 166 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.7 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 0x483e0898 - 0x483e08f0
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
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.
sh_cmt sh-cmt-48-gen2.0: ch1: cannot clear CMCNT
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.
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: Failed to add - passthrough or MSI/MSI-X might fail!
pci 0000:01:01.0: Failed to add - passthrough or MSI/MSI-X might fail!
pci 0000:01:02.0: Failed to add - passthrough or MSI/MSI-X might fail!
PCI: bus1: Fast back to back transfers disabled
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: Failed to add - passthrough or MSI/MSI-X might fail!
pci 0000:02:01.0: Failed to add - passthrough or MSI/MSI-X might fail!
pci 0000:02:02.0: Failed to add - passthrough or MSI/MSI-X might fail!
PCI: bus2: Fast back to back transfers disabled
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:3d:d3, 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
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
Key type dns_resolver registered
ata1: link resume succeeded after 1 retries
sh_mobile_sdhi sh_mobile_sdhi.0: mmc1 base at 0xee100000 clock rate 97 MHz
ata1: SATA link down (SStatus 0 SControl 300)
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)
vqmmc: disabling
ALSA device list:
  #0: SSI01-AK4643
Waiting for root device /dev/mmcblk1p1...
mmc0: BKOPS_EN bit is not set
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 MMC08G 7.32 GiB 
mmcblk0boot0: mmc0:0001 MMC08G partition 1 2.00 MiB
mmcblk0boot1: mmc0:0001 MMC08G partition 2 2.00 MiB
 mmcblk0: p1
mmc1: new high speed SDHC card at address 1234
mmcblk1: mmc1:1234 SA16G 14.4 GiB 
 mmcblk1: p1
EXT4-fs (mmcblk1p1): mounting ext2 file system using the ext4 subsystem
EXT4-fs (mmcblk1p1): warning: mounting unchecked fs, running e2fsck is recommended
EXT4-fs (mmcblk1p1): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext2 filesystem) on device 179:25.
devtmpfs: mounted
Freeing unused kernel memory: 168K (c04d6000 - c0500000)
random: nonblocking pool is initialized
systemd[1]: systemd 216 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN )
systemd[1]: Detected virtualization 'xen'.
systemd[1]: Detected architecture 'arm'.

Welcome to Automotive Grade Linux 1.0.0!

systemd[1]: Failed to insert module 'autofs4'
systemd[1]: Failed to insert module 'ipv6'
systemd[1]: Set hostname to <lager>.
systemd[1]: Configuration file /lib/systemd/system/weston.service is marked executable. Please remove executable permission bits. Proceeding anyway.
systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory.
systemd[1]: Expecting device dev-hvc0.device...
         Expecting device dev-hvc0.device...
systemd[1]: Expecting device dev-ttySC6.device...
         Expecting device dev-ttySC6.device...
systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
systemd[1]: Started Forward Password Requests to Wall Directory Watch.
systemd[1]: Starting Remote File Systems.
[  OK  ] Reached target Remote File Systems.
systemd[1]: Reached target Remote File Systems.
systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
systemd[1]: Starting Paths.
[  OK  ] Reached target Paths.
systemd[1]: Reached target Paths.
systemd[1]: Starting Swap.
[  OK  ] Reached target Swap.
systemd[1]: Reached target Swap.
systemd[1]: Starting Root Slice.
[  OK  ] Created slice Root Slice.
systemd[1]: Created slice Root Slice.
systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
systemd[1]: Starting Delayed Shutdown Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
systemd[1]: Listening on Delayed Shutdown Socket.
systemd[1]: Starting Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
systemd[1]: Listening on Journal Socket (/dev/log).
systemd[1]: Starting Syslog Socket.
[  OK  ] Listening on Syslog Socket.
systemd[1]: Listening on Syslog Socket.
systemd[1]: Starting User and Session Slice.
[  OK  ] Created slice User and Session Slice.
systemd[1]: Created slice User and Session Slice.
systemd[1]: Starting udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
systemd[1]: Listening on udev Kernel Socket.
systemd[1]: Starting udev Control Socket.
[  OK  ] Listening on udev Control Socket.
systemd[1]: Listening on udev Control Socket.
systemd[1]: Starting Journal Socket.
[  OK  ] Listening on Journal Socket.
systemd[1]: Listening on Journal Socket.
systemd[1]: Starting System Slice.
[  OK  ] Created slice System Slice.
systemd[1]: Created slice System Slice.
systemd[1]: Started File System Check on Root Device.
systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
systemd[1]: Started Create list of required static device nodes for the current kernel.
systemd[1]: Started Load Kernel Modules.
systemd[1]: Mounted Huge Pages File System.
systemd[1]: Mounting Configuration File System...
         Mounting Configuration File System...
systemd[1]: Starting Apply Kernel Variables...
         Starting Apply Kernel Variables...
systemd[1]: Mounted FUSE Control File System.
systemd[1]: Mounted Debug File System.
systemd[1]: Mounted POSIX Message Queue File System.
systemd[1]: Starting system-getty.slice.
[  OK  ] Created slice system-getty.slice.
systemd[1]: Created slice system-getty.slice.
systemd[1]: Starting system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
systemd[1]: Created slice system-serial\x2dgetty.slice.
systemd[1]: Starting udev Coldplug all Devices...
         Starting udev Coldplug all Devices...
systemd[1]: Starting Journal Service...
EXT4-fs (mmcblk1p1): re-mounted. Opts: (null)
         Starting Journal Service...
[  OK  ] Started Journal Service.
systemd[1]: Started Journal Service.
[  OK  ] Reached target Slices.
         Mounting Temporary Directory...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Mounted Temporary Directory.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /var/volatile...
[  OK  ] Mounted /var/volatile.
         Starting Load/Save Random Seed...
systemd-udevd[920]: starting version 216
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Trigger Flushing of Journal to Persistent Storage...
[  OK  ] Started udev Kernel Device Manager.
         Starting Start Psplash Boot Screen...
[  OK  ] Started Load/Save Random Seed.
systemd-journald[568]: Received request to flush runtime journal from PID 1
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[  OK  ] Started Start Psplash Boot Screen.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Reached target System Time Synchronized.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target Sound Card.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Found device /dev/ttySC6.
[  OK  ] Found device /dev/hvc0.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on dropbear.socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
         Starting Restore Sound Card State...
[  OK  ] Reached target Basic System.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Kernel Logging Service...
[  OK  ] Started Kernel Logging Service.
         Starting System Logging Service...
[  OK  ] Started System Logging Service.
         Starting Terminate Psplash Boot Screen...
         Starting Automotive Message Broker...
         Starting Telephony service...
         Starting (null)...
         Starting Login Service...
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Telephony service.
         Starting Network Service...
         Starting Permit User Sessions...
[  OK  ] Started Restore Sound Card State.
[FAILED] Failed to start Terminate Psplash Boot Screen.
See 'systemctl status psplash-quit.service' for details.
[  OK  ] Started (null).
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Network Service.
[  OK  ] Started Login Service.
         Starting Bluetooth service...
[  OK  ] Reached target Network.
         Starting Serial Getty on ttySC6...
[  OK  ] Started Serial Getty on ttySC6.
         Starting Serial Getty on hvc0...
[  OK  ] Started Serial Getty on hvc0.
[  OK  ] Reached target Login Prompts.
         Starting Weston reference Wayland compositor...
[  OK  ] Started Weston reference Wayland compositor.
[  OK  ] Started Bluetooth service.
[  OK  ] Created slice user-0.slice.
         Starting User Manager for UID 0...
[  OK  ] Started Automotive Message Broker.
[  OK  ] Reached target Multi-User System.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
[  OK  ] Started User Manager for UID 0.
 


[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-22 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:23 Error regarding filesystem in Dom0 in lager board George John
2016-11-16 18:08 ` Iurii Mykhalskyi
2016-11-18 14:18   ` George John
2016-11-18 21:05   ` Julien Grall
2016-11-18 21:36 ` Julien Grall
2016-11-20 15:44   ` George John
2016-11-21 11:15     ` Andrii Anisov
2016-11-22 17:40       ` George John [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANou6Srkzb83kerTRnpZ_c50cRkzqf9pishnLzpdM77V==vx0w@mail.gmail.com' \
    --to=georgeeldhojohn@gmail.com \
    --cc=andrii.anisov@gmail.com \
    --cc=julien.grall@arm.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.