From: George John <georgeeldhojohn@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Error regarding filesystem in Dom0 in lager board
Date: Sun, 20 Nov 2016 21:14:45 +0530 [thread overview]
Message-ID: <CANou6Sof3o-OC_=2qvKifeCJS82NogZb3nRDJNjsZFSf=v7ekw@mail.gmail.com> (raw)
In-Reply-To: <de2acd07-e143-c43d-6ae1-0f5f96a8bc1b@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1868 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 3173 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-20 15:44 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 [this message]
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='CANou6Sof3o-OC_=2qvKifeCJS82NogZb3nRDJNjsZFSf=v7ekw@mail.gmail.com' \
--to=georgeeldhojohn@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.