Can't start L4Linux-2.6.18

[Adam Lackorzynski]

On Mon Dec 04, 2006 at 16:14:17 +0100, FERANDELLE Pascal wrote:
> > > ...
> > > l4lx    | ======> L4Linux 2.6 starting... <========
> > > l4lx    | Linux version 2.6.18-l4 (root at PClinux) (gcc version 3.4.6) #1 Fri Dec
> > > l4lx    :  1 18:41:42 CET 2006
> > > l4lx    | Binary name: vmlinuz26
> > > l4lx    | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load
> > > l4lx    : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd
> > > l4lx    | The running kernel does not have the
> > > l4lx    |       exception_ipc
> > > l4lx    | feature enabled!
> > >
> > > Of course, I have the exception_ipc feature enabled in Fiasco !!!
> >
> > By any chance, do you have CONFIG_REGPARM enabled? Disable it.
> > (I recently added a check for that config option...)
> 
> I disable it, in both Fiasco and L4Linux, and now L4Linux is starting.
> But, it panics ...
> Here is the end of the log on the serial line :
> 
> ...
> Kernel command line: earlyprintk=yes mem=64M load_ramdisk=1 ramdisk_size=16384 r
> oot=/dev/ram l4env_rd=test-rd.rd
> Initializing CPU#0
> l4lx_irq_init: l4lx_irq_max = 18
> PID hash table entries: 512 (order: 9, 2048 bytes)
> l4lx_irq_timer_startup(0)
> l4lx    | l4lx_thread_create: Created thread 0e.05 (timer.i0)
> timer_irq_thread: Starting timer IRQ thread.
> disabling early console
> l4lx    | l4lx_thread_create: Created thread 0e.06 (Idler)
> l4lx    | Starting L4FB via CON
> con     | vc_loop(): vc[1] running as B.07
> l4lx    | l4lx_thread_create: Created thread 0e.07 (L4ConInput)
> con     | vc_open_out(): vc[1] 1024x768 at 16, gmode:0x35
> l4lx    | l4fbcon: 1024x750 2bypp, size: 1540096
> l4lx    | l4lx_thread_create: Created thread 0e.08 (CON refresher)
> l4lx    | l4lx_thread_create: Created thread 0e.09 (IRQ8)
> l4lx    | panic: going to sleep forever, bye
> 
> and on my graphical console :
> 
> ...
> EFLAGS : 00013202 (2.6.18-l4 #3)
> EIP is at flush_kernel_map+0x9/0x10
> 

> Call Trace :
> Global_flush_tlb
> agp_backend_initialize
> pci_enable_device
> agp_add_bridge

Do not enable AGP, I think that's the culprit.



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