Messages in this thread |  | | Date | Mon, 9 Sep 2002 20:53:55 +0200 (CEST) | From | Ingo Molnar <> | Subject | do_syslog/__down_trylock lockup in current BK |
| |
i can reproduce the following lockup in BK-current, SMP:
>>EIP; c0106c57 <__down_trylock+a7/b4> <===== Trace; c0120316 <do_syslog+16/6a0> Trace; c01088c8 <show_registers+198/1c0> Trace; c011ef16 <do_fork+436/b20> Trace; c011f41a <do_fork+93a/b20> Trace; c0125755 <release_resource+15/50> Trace; c0126686 <proc_doutsstring+76/c0> Trace; c0127c54 <__constant_copy_from_user+24/98> Trace; c0107cf3 <handle_signal+113/1a0> Trace; c012d572 <sys_setreuid+22/170> Trace; c0107fce <do_signal+24e/3c0>
it could be related to the signal changes - but at first sight it looks like some sort of printk related lockup.
Ingo
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |