Re: [Xen-devel] Error regarding filesystem in Dom0 in lager board

[George John <georgeeldhojohn@xxxxxxxxx>]

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@xxxxxxxxx> 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@xxxxxxxxx> wrote:
> Hi,
>
>
> On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall <julien.grall@xxxxxxx> 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@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
>

Attachment: log_22-11-2016
Description: Binary data

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