|
From: <zl...@tc...> - 1999-12-21 19:41:12
|
This is the backtrace:
(gdb) backtrace
#0 panic (
fmt=0x1013eea0 "wait_for_stop failed to wait for %d to stop with %d\n")
at panic.c:86
#1 0x1006e322 in wait_for_stop (pid=1865, sig=19) at user_util.c:285
#2 0x100696a4 in start_fork_tramp (saved_regs=0x50554228,
sig_stack=1349529600) at process.c:115
#3 0x1006ab11 in do_proc_op (pid=1864) at process_kern.c:233
#4 0x1006d4a2 in signals (arg=0xbffff5e8) at trap_user.c:119
The output of /proc/1579/stat:
1579 (linux) R 1578 1577 770 768 1577 64 1 277 467 98450 50014 425 549 1014 13 0
0 0 1275700 10186752 519 2147483647 268435456 269189368 3221223072 1342189300 2
68455457 0 0 0 3584 0 0 0 17
Zbigniew
Jeff Dike wrote:
> > Starting INET services: process stopped with signal 11
> > Kernel panic: wait_for_stop failed to wait for 1399 to stop with 19
>
> OK, I like these bugs better.
>
> Attach gdb to the signal thread pid, which is in the first line of the boot
> output, and get a backtrace.
>
> Then, get the output /proc/<pid>/stat, where <pid> is the pid in the panic
> message and send that to me as well.
>
> Also, I reproduced the original crond bug, I think. I'll fix that and get
> back to you.
> Jeff
>
>
>
> _______________________________________________
> User-mode-linux-user mailing list
> Use...@li...
> http://lists.sourceforge.net/mailman/listinfo/user-mode-linux-user
|