Aw: Re: l4linux starting - How can I see all Debug messages on serial line ?

 
 

>Gesendet: Samstag, 27. Juli 2013 um 23:56 Uhr
>Von: "Adam Lackorzynski" <[email protected]>
>An: "Rudolf Weber" <[email protected]>
>Cc: "l4 l4hackerlist" <[email protected]>
>Betreff: Re: l4linux starting - How can I see all Debug messages on serial line ?
>Hi,

>On Fri Jul 26, 2013 at 14:55:13 +0200, Rudolf Weber wrote:
>> Gesendet: Donnerstag, 25. Juli 2013 um 23:50 Uhr
>> Von: "Adam Lackorzynski" <[email protected]>
>> An: "Rudolf Weber" <[email protected]>
>> Cc: "l4 l4hackerlist" <[email protected]>
>> Betreff: Re: l4linux starting - How can I see all Debug messages on serial line ?
>> >> Question1: How can I see the error messages of L4linux on serial lines?
>> >Add console=ttyLv0 to the L4Linux argument list.
>> So I can see the output on all configurations.
>>
>> The state is now:
>> 1) Linux-conf x86-ux_defconfig without mag : runs
>> 2) Linux-conf x86-ux_defconfig with mag : runs
>> 3) Linux-conf x86_rw_config without mag : runs
>> 4) Linux-conf x86_rw-config with mag : error
>>
>> My x86_rw-config is in the Attachment.
>> The error is:
>>
>> attempt to access beyond end of device
>> ram0: rw=0, want=4764729332, limit=8000
>> Buffer I/O error on device ram0, logical block 2382364665
>> attempt to access beyond end of device
>> ram0: rw=0, want=4606413050, limit=8000
>> Buffer I/O error on device ram0, logical block 2303206524
>>
>> Attachement log_ioerror ist the whole output.
>>
>> Why this IO-Error ?
>> Does something overwrites the ramdisk ? Or is the ramdisk shortened ?
>>
>> I give in qemu 1024M and Linux in the cmdline 128M,but the phenomenon is still there.

>When the ramdisk is too big for Linux, it will complain.
>Since the same config works when not starting mag(?) does it work when
>just not giving the fb cap to L4Linux?

Yes, I reproduced again by modifing the configuratin:
* adding fb_drv - in the list - it works
* without mag it works, with mag it failes.
* If I don't give the fb-cap to L4Linux,  I can't see the l4linux-Window - this is what I expect.

I now put the mag-module as last module (behind the ramdisk for linux) - I expect, the order of further modules don't matter
->/home/rw/l4exp/l4re-snapshot-2013060718/src/l4/pkg/bootstrap/server/src/startup.cc:526: void try_move_module(const Region&, l4util_mb_info_t*, unsigned int, long unsigned int, unsigned int): Assertion `to' failed.
-> unsigned long long to = regions.find_free(module_area, size, L4_PAGESHIFT);
   returns null

May this destroy the ramdisk too ?

(Oh, I remember: I applied the patch from http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/005903.html
 to fix the bootstrap-problemon x86_64 of the hello world-Application.
 Since l4linux is not ported to x86_64, I tried x86)

Greetings
  Rudolf

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers