logo       

Re: [uml-user] 2.6.3 hang on boot: msg#00300

Subject: Re: [uml-user] 2.6.3 hang on boot
Alle 07:51, lunedì 23 febbraio 2004, MeiJia ha scritto:
> BlaisorBlade wrote:

> Thanks you very much for the reply!
>
> for some reason I must use 2.6.3. following is the
> backtrace:

> (gdb) bt
> #0  0xa011f4a1 in sigprocmask () at seq_file.h:49
> #1  0xa00173c2 in change_sig (signal=10, on=1)
>     at arch/um/kernel/signal_user.c:56
> #2  0xa001cb70 in sig_handler_common_tt (sig=11,
> sc_ptr=0x58)
>     at arch/um/kernel/tt/trap_user.c:33
> #3  0xa001955f in sig_handler (sig=-1577124956, sc=
>       {gs = 7, __gsh = 0, fs = 0, __fsh = 0, es = 123,
> __esh = 0, ds = 123, __dsh = 0, edi = 134534120, esi =
> 1073828704, ebp = 2684354264, esp = 2684354216, ebx =
> 18, edx = 2684354522, ecx = 791621423, eax = 60,
> trapno = 14, err = 6, eip = 2686245736, cs = 115,
> __csh = 0, eflags = 2163270, esp_at_signal =
> 2684354216, ss = 123, __ssh = 0, fpstate = 0xa1fefd80,
> oldmask = 134283264, cr2 = 60})
>     at arch/um/kernel/trap_user.c:102
> #4  <signal handler called>
> #5  0xa01cdb68 in __kernel_vsyscall ()
> Previous frame inner to this frame (corrupt stack?)
> (gdb)
>
> At the hang time, the two processes which occupy all
> CPU power is:
> - 1090 pts/0    S      0:12 ./linux [(tracing thread)]
> - 1122 pts/0    R      0:17 ./linux [/sbin/init]
>
> AFAIK, tracing thread only get control when process
> within UML issue syscalls. So it looks like /sbin/init
> is trying to do something via syscalls, but always
> failed, so it repeatedly issue out syscalls?

Ok. That seems to be another different beast. The problem is with the RH9 
filesystem. The RH9 kernel uses the "vsyscall" kernel feature which comes 
from 2.6. But UML does not (yet) support "vsyscall". So I think that the the 
problem is with the filesystem. Use an older one (RH8 should be good) or one 
not RH.

Actually, the tracing thread is not handling syscalls, but SIGSEGV: init tries 
to use vsyscall (which involves jumping into a certain memory area), that 
area is not allocated so it SIGSEGV, and the tracing thread must handle this.

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click


<Prev in Thread] Current Thread [Next in Thread>