From owner-freebsd-xen@FreeBSD.ORG Mon Mar 17 18:45:02 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EC998B4 for ; Mon, 17 Mar 2014 18:45:02 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id CA599A51 for ; Mon, 17 Mar 2014 18:45:01 +0000 (UTC) Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s2HIiuZq098550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Mar 2014 18:44:57 GMT Date: Mon, 17 Mar 2014 18:44:56 +0000 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@FreeBSD.org Subject: Re: FBSD 10.0-S (r261289M) under XenServer 6.2 - Stuck sshd in urdlck? Message-ID: <6534613783544E26A15CF44F@study64.tdx.co.uk> In-Reply-To: <53272E41.3050409@citrix.com> References: <4B8380EBE379080FAD3271FA@Mail-PC.tdx.co.uk> <53272E41.3050409@citrix.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2014 18:45:02 -0000 --On 17 March 2014 18:17:53 +0100 Roger Pau Monn=C3=A9 = =20 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 ? procstat output is: " # procstat -k 5334 PID TID COMM TDNAME KSTACK 5334 100183 sshd - mi_switch=20 sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_rw_rdlock=20 __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=20 machine (i.e. cause a crash-dump?) somehow? Cheers & thanks for your reply, -Karl