From mboxrd@z Thu Jan 1 00:00:00 1970 From: George John Subject: Re: Error regarding filesystem in Dom0 in lager board Date: Sun, 20 Nov 2016 21:14:45 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6144574572949297221==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c8UIT-00020H-1r for xen-devel@lists.xenproject.org; Sun, 20 Nov 2016 15:44:49 +0000 Received: by mail-oi0-f50.google.com with SMTP id z62so137202987oiz.1 for ; Sun, 20 Nov 2016 07:44:46 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Julien Grall Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org --===============6144574572949297221== Content-Type: multipart/alternative; boundary=001a113e39e4254a9f0541bd6b77 --001a113e39e4254a9f0541bd6b77 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall 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 MH= z >> 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 M= Hz >> asoc-simple-card asoc-simple-card: ak4642-hifi <-> rcar_sound mapping ok >> input: gpio-keys as /devices/platform/gpio-keys/input/input0 >> =EF=BF=BDH=EF=BF=BDEXT4-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 --001a113e39e4254a9f0541bd6b77 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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<= br> 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<= br> asoc-simple-card asoc-simple-card: ak4642-hifi <-> rcar_sound mapping= ok
input: gpio-keys as /devices/platform/gpio-keys/input/input0
=EF=BF=BDH=EF=BF=BDEXT4-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 fil= esystem with fsck?

<= div>No, I haven't verified the filesystem. But the filesystem is workin= g 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.
=C2=A0

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.

Ye= s, I have tried that. Xen is also becoming inaccessible. Nothing works afte= r the system hang.
=C2=A0

Regards,

--
Julien Grall


Regards,=
George

--001a113e39e4254a9f0541bd6b77-- --===============6144574572949297221== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============6144574572949297221==--