From: <se...@ex...> - 2004-06-26 20:33:29
|
Hi, finally I was able to produce this stracktrace with 2.4.26-um1 (host also 2.4.26) It happend during a mysql-server start. (I can reproduce this quite constant, if you have further questions ...) maybe something with ipc ? Breakpoint 1, panic (fmt=0x0) at panic.c:58 58 machine_paniced = 1; (gdb) bt #0 panic (fmt=0x0) at panic.c:58 #1 0xa008e04b in segv (address=28, ip=1818324839, is_write=2, is_user=0, sc=0x0) at trap_kern.c:144 #2 0xa008e3d7 in segv_handler (sig=11, regs=0xa13ec274) at trap_user.c:67 #3 0xa0090ea4 in sig_handler_common_skas (sig=11, sc_ptr=0x58) at trap_user.c:35 #4 0xa008e408 in sig_handler (sig=0, sc= {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 2, esi = 28, ebp = 2705260500, esp = 2705260428, ebx = 0, edx = 0, ecx = 2684354560, eax = 28, trapno = 14, err = 6, eip = 2684935257, cs = 35, __csh = 0, eflags = 66194, esp_at_signal = 2705260428, ss = 43, __ssh = 0, fpstate = 0x0, oldmask = 134217728, cr2 = 28}) at trap_user.c:101 #5 <signal handler called> #6 0xa008dc59 in handle_page_fault (address=1881171332, ip=0, is_write=2, is_user=0, code_out=0xa13f0024) at rwsem.h:101 #7 0xa008df56 in segv (address=1881171332, ip=0, is_write=2, is_user=0, sc=0x1c) at trap_kern.c:133 #8 0xa008e3d7 in segv_handler (sig=11, regs=0xa13f0274) at trap_user.c:67 #9 0xa0090ea4 in sig_handler_common_skas (sig=11, sc_ptr=0x58) at trap_user.c:35 #10 0xa008e408 in sig_handler (sig=28, sc= {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 0, esi = 1881171332, ebp = 2705261644, esp = 2705261572, ebx = 188117---Type <return> to continue, or q <return> to quit--- /sebastian |
From: BlaisorBlade <bla...@ya...> - 2004-06-27 15:51:01
|
Alle 22:24, sabato 26 giugno 2004, Sebastian B=F6hm ha scritto: > Hi, > > finally I was able to produce this stracktrace with 2.4.26-um1 (host > also 2.4.26) > It happend during a mysql-server start. (I can reproduce this quite > constant, if you have further questions ...) Very well, a reproducible crash is very important. > maybe something with ipc ? > Breakpoint 1, panic (fmt=3D0x0) at panic.c:58 > 58 machine_paniced =3D 1; > (gdb) bt > #10 0xa008e408 in sig_handler (sig=3D28, sc=3D > {gs =3D 0, __gsh =3D 0, fs =3D 0, __fsh =3D 0, es =3D 43, __esh =3D= 0, ds =3D > 43, __dsh =3D 0, edi =3D 0, esi =3D 1881171332, ebp =3D 2705261644, esp = =3D > 2705261572, ebx =3D 188117 Eeeh? > ---Type <return> to continue, or q <return> to quit--- Aargh! Why did not you type <return> here? The backtrace still continues, a= nd=20 the part you posted is the least significant one (though there is already=20 something strange - a panic onto a panic - but not yet enough). It's like a= =20 joke from the fate.... Just post the *complete* backtrace and I'll be able to start to analyze the= =20 bug. =2D-=20 Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |
From: BlaisorBlade <bla...@ya...> - 2004-06-28 17:40:51
|
Alle 22:32, domenica 27 giugno 2004, Sebastian B=F6hm ha scritto: > BlaisorBlade wrote: > Can I exit gdb now ? Or is there something more ? Well, maybe you can. There is a patch onto the ML (not from me), with this= =20 title: [uml-devel] Patch for arch/um/kernel/trap_kern.c to fix bad panic And I think it could fix exactly your problem. At least, retry with that=20 applied; and say me whether things become safe or not. However, I'm not sur= e=20 it does relate to that bug. > I posted the complete output to user-mode-linux-devel, did you noticed th= at=20 ? I received all your mails, now, but I'm not always online so when I wrote t= hat=20 mail I hadn't it yet. Bye =2D-=20 Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |