All of lore.kernel.org
 help / color / mirror / Atom feed
From: George John <georgeeldhojohn@gmail.com>
To: Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Error regarding filesystem in Dom0 in lager board
Date: Fri, 18 Nov 2016 19:48:53 +0530	[thread overview]
Message-ID: <CANou6Sq1Vb3WJ8rS5resotN5_VeRCfAK3He3_4aic0J0e8RCkg@mail.gmail.com> (raw)
In-Reply-To: <CAC+yBMuWXkna5Cio8=2g4E8bjvywV5x8_j_8e4ntyhs3p=sF_A@mail.gmail.com>


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

Ok thanks for the reply, I have applied the dts file. My observations are:

Adding hypervisor node has no effect on booting. For me even without
hypervisor node it is getting booted up to mounting filesystem. After that
point the system hangs as given in the log.

Adding psci node results in breakdown of Xen. Xen gets crashed without
booting linux DOM0.

regards,
George



On Wed, Nov 16, 2016 at 11:38 PM, Iurii Mykhalskyi <
iurii.mykhalskyi@globallogic.com> wrote:

> Hi,
>
> Try to use attached files as DTS. I didn't tested, but looks like there
> are few missed nodes:
> - hypervisor
> - psci
>
> I'm not sure, that Linux & Xen will correctly inter-works without them.
>
> With the best regards,
> Iurii Mykhalskyi
>
>
>
> On Wed, Nov 16, 2016 at 7:23 PM, George John <georgeeldhojohn@gmail.com>
> wrote:
>
>> Hi,
>> 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
>>
>> 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]: 0000000040ef2000 - 0000000040efe000 Device Tree
>> (XEN) MODULE[1]: 0000000072000000 - 00000000722a0660 Kernel
>> (XEN) MODULE[2]: 0000000074000000 - 000000007400284f XSM
>> (XEN)  RESVD[0]: 000000007ff9a000 - 000000007ff9a120
>> (XEN)  RESVD[1]: 0000000040ef2000 - 0000000040efe000
>> (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 "serial0", options "38400n8"
>> (XEN) WARNING: UART configuration is not supported
>>  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 Mon Nov  7 11:44:45
>> 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 64 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) 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 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-000000004fe79fb8
>> (XEN) Allocating PPI 16 for event channel interrupt
>> (XEN) Loading dom0 DTB to 0x0000000050000000-0x000000005000ab70
>> (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.
>> 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) ) #23 Mon Nov 14 17:20:55 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 #23
>> Hardware name: lager
>> Backtrace:
>> [<c00121f4>] (dump_backtrace) from [<c0012388>] (show_stack+0x18/0x1c)
>>  r6:c0476ecb r5:00000009 r4:00000000 r3:00200000
>> [<c0012370>] (show_stack) from [<c03cf7f4>] (dump_stack+0x20/0x28)
>> [<c03cf7d4>] (dump_stack) from [<c0021ba4>] (warn_slowpath_common+0x88/0xb
>> 0)
>> [<c0021b1c>] (warn_slowpath_common) from [<c0021c38>]
>> (warn_slowpath_fmt+0x38/0x40)
>>  r8:c04fbee8 r7:e6b187dc r6:00000001 r5:00000000 r4:e6b18a44
>> [<c0021c04>] (warn_slowpath_fmt) from [<c04c228c>]
>> (arm_dt_init_cpu_maps+0xc0/0x12c)
>>  r3:00000002 r2:c0476f0e
>> [<c04c21cc>] (arm_dt_init_cpu_maps) from [<c04c1964>]
>> (setup_arch+0x5e0/0x78c)
>>  r7:c04f3708 r6:c052af98 r5:c04de83c r4:e6b18f80
>> [<c04c1384>] (setup_arch) from [<c04bf9c4>] (start_kernel+0x80/0x33c)
>>  r10:00000000 r9:c04f0000 r8:48004059 r7:ffffffff r6:c0512b40 r5:00000001
>>  r4:00000000
>> [<c04bf944>] (start_kernel) from [<48008070>] (0x48008070)
>>  r10:00000000 r9:413fc0f2 r8:48004059 r7:c04f3810 r6:c04dfbf8 r5:c04f0078
>>  r4:c05135d4
>> ---[ 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  rw root=/dev/mmcblk0p1 rootfstype=ext2
>> rdinit=/sbin/init rootwait fixrtc
>> 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: 627628K/638976K available (3887K kernel code, 170K rwdata, 936K
>> rodata, 164K init, 164K bss, 11348K 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 - 0xc04befb4   (4828 kB)
>>       .init : 0xc04bf000 - 0xc04e8000   ( 164 kB)
>>       .data : 0xc04e8000 - 0xc0512b40   ( 171 kB)
>>        .bss : 0xc0512b40 - 0xc053bdb8   ( 165 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 0x483d32b0 - 0x483d3308
>> 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
>> 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.
>> Switched to clocksource sh-cmt-48-gen2.0
>> 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)
>> sh_cmt sh-cmt-48-gen2.0: ch0: used for oneshot clock events
>> 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
>> 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
>> mmc0: BKOPS_EN bit is not set
>> mmc0: new high speed MMC card at address 0001
>> 1DEBUG: Passed mmc_add_card 317
>> 2DEBUG: Passed mmc_add_card 319
>> 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
>> 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
>>
>>
>>
>> After this the system hangs
>> I am trying to debug the issue
>> please help
>> I am attaching the dts file I have used for the lager board.
>>
>> Regards,
>> George
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> https://lists.xen.org/xen-devel
>>
>>
>
>
> --
>
> Iurii Mykhalskyi | Senior 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
>

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

[-- Attachment #2: 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-18 14:18 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 [this message]
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

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=CANou6Sq1Vb3WJ8rS5resotN5_VeRCfAK3He3_4aic0J0e8RCkg@mail.gmail.com \
    --to=georgeeldhojohn@gmail.com \
    --cc=iurii.mykhalskyi@globallogic.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.