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

[Adam Lackorzynski]

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" <adam at os.inf.tu-dresden.de>
> An: "Rudolf Weber" <rwib at web.de>
> Cc: "l4 l4hackerlist" <l4-hackers at os.inf.tu-dresden.de>
> 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?



Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/