Hi,
On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall <julien.gr...@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
