On 28 Feb 2015, at 19:39, [email protected] wrote: > On Sat, 28 Feb 2015, J. Hannken-Illjes wrote: >> >> This one looks bad. Which thread holds proc_lock? >> > > Helps this? > > https://www.ipv6.uni-leipzig.de/proc_lock.png
Looks unlocked -- what about a backtrace of thread 0.5, bt /a 0xfffffe882df11860 -- J. Hannken-Illjes - [email protected] - TU Braunschweig (Germany)
