--On 17 March 2014 18:17:53 +0100 Roger Pau Monné <roger....@citrix.com> wrote:

Anyone know what 'urdlck' is?

It seems like the process is stuck while trying to acquire a rw mutex in
read mode. Could you obtain a backtrace of the process with gdb?

Ok, I think I did this right - let me know if I've not...

# gdb /usr/sbin/sshd 5325
Attaching to program: /usr/sbin/sshd, process 5325

warning: current_sos: Can't read pathname for load map: Bad address
[repeated several times]
[lots of reading symbols from - 'no debugging symbols found' output]
[New Thread 804006400 (LWP 100184/sshd)]
[a few reading symbols - 'no debugging symbols found' output]
Loaded symbols for /libexec/ld-elf.so.1
[Switching to Thread 804006400 (LWP 100184/sshd)]
0x00000008038eb89c in __error () from /lib/libthr.so.3
(gdb) bt
#0  0x00000008038eb89c in __error () from /lib/libthr.so.3
#1  0x00000008038e921c in pthread_timedjoin_np () from /lib/libthr.so.3
#2  0x000000080064f9a2 in _rtld_get_stack_prot () from /libexec/ld-elf.so.1
#3  0x00000008006498c9 in r_debug_state () from /libexec/ld-elf.so.1
#4  0x00000008006470cd in .text () from /libexec/ld-elf.so.1
#5  0x0000000000000246 in ?? ()
#6  0x0000000000000000 in ?? ()

Also a
kernel-space dump might be useful, could you also run procstat -k <pid>?

procstat output is:

# procstat -k 5334
 PID    TID COMM             TDNAME           KSTACK
5334 100183 sshd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_rw_rdlock __umtx_op_rw_rdlock amd64_syscall Xfast_syscall

If you can briefly tell me how to do the kernel-space dump? Do I panic the machine (i.e. cause a crash-dump?) somehow?

Cheers & thanks for your reply,


freebsd-xen@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to