[lkml]   [2002]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectdo_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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.046 / U:0.824 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site