About build of L4Linux

[Adam Lackorzynski]

On Sat Jul 14, 2007 at 06:26:49 +0900, Lin wrote:
> >Please enable EARLY_PRINTK in the L4Linux configuration (under Kernel
> >hacking) and add "earlyprintk=yes" to the Linux kernel command line.
> >This should give us more output.
> 
> I enabled them and found new messages from kernel.
> 
> ----------------------------------------------------------------------
> .....
> Linux version 2.6.21-l4 () (gcc version 3.4.6 20060404 (Red Hat
> 3.4.6-4)) #9 Sat Jul 14 05:08:25 JST 2007
> CPU: Vendor unknown, using generic init.
> CPU: Your system may be unstable.
> dm_phys: 0000000000800000 - 0000000010800000 (usable)
> 256MB memory available.
> Zone PFN ranges:
>  DMA             0 ->      512
>  Normal        512 ->    67584
> early_node_map[1] active PFN ranges
>    0:        0 ->    67584
> Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
> Built 1 zonelists.  Total pages: 67056
> Kernel command line: earlyprintk=yes console=ttyS1,115200 init=1
> mem=256M root=/dev/hda1
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 8192 bytes)
> Detected 1995.013 MHz processor.
> disabling early console
> l4lx    | l4lx_thread_create: Created thread 0d.05 (timer.i0)
> l4lx    | l4lx_thread_create: Created thread 0d.06 (Idler)
> ----------------------------------------------------------------------
> 
> Is the message "CPU: Your system may be unstable." abnormal ?
> I'm running L4Linux on LV-673 (with Pentium M cpu).
> (http://www.commell.com.tw/Product/SBC/LV-673.HTM)
> Of course, I set the "target processor" Pentium M in fiasco and
> L4Linux configurations.

This message sounds harmless.
 
> I attached the log which all of serial output are written in.
> I could not find any messages which is relate to this freeze.
> Do you have anything about it ?

The kernel command line says that the kernel output goes to the second
serial interface. Obviously you won't see more Linux kernel messages in
the Fiasco debug log as well as in any Dope window. Do you see something
on ttyS1? If you want to see more messages in the debug log, enable the
"serial driver" under "stub drivers" in L4Linux and replace the
console=... option with console=ttyLv0
If you leave it out or write console=tty0 the output will go to the Dope
window.



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