On 2011-09-28, Anton Shterenlikht wrote: > KDB: stack backtrace: > getenv with the following non-sleepable locks held: > exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe000000011950488) locked _at_ /usr/src/sys/fs/devfs/devfs_vnops.c:406 > > etc. until a hang, requiring cold reset via MP. Someone is calling getenv with a vnode interlock held. You need to figure out the caller. Unfortunately the backtrace is missing above. As a temporary workaround you could comment the WITNESS_WARN() line in getenv() (sys/kern/kern_environment.c) but it is not a real fix. -- JaakkoReceived on Wed Sep 28 2011 - 11:27:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:18 UTC