In article <[email protected]>, Tom Ivar Helbekkmo <[email protected]> wrote: >I tried building a kernel with LOCKDEBUG, but that hung about halfway >through the /etc/rc.d/ scripts, so I gave up on it. I've just managed >to get a proper core dump from a hang. Didn't write down the backtraces >for the various CPUs, but one was doing disk I/O, one was in pf handling >a fragment (and calling kernel_lock()), one was in ipmi (again, calling >kernel_lock(), I think), and the final one was servicing some interrupt. > >If there's anything I ought to pull from the dump, please let me know!
If LOCKDEBUG hangs, you have problems.... I'd try to get more information on that first. christos
