From owner-freebsd-bugs@FreeBSD.ORG Fri Mar 23 16:20:12 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE6301065677 for ; Fri, 23 Mar 2012 16:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D54A88FC1B for ; Fri, 23 Mar 2012 16:20:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2NGKBDX072861 for ; Fri, 23 Mar 2012 16:20:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2NGKBU9072860; Fri, 23 Mar 2012 16:20:11 GMT (envelope-from gnats) Resent-Date: Fri, 23 Mar 2012 16:20:11 GMT Resent-Message-Id: <201203231620.q2NGKBU9072860@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Christian Esken Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0DAC61065676 for ; Fri, 23 Mar 2012 16:18:44 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id D33BF8FC1F for ; Fri, 23 Mar 2012 16:18:43 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q2NGIhPk036717 for ; Fri, 23 Mar 2012 16:18:43 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q2NGIhp4036716; Fri, 23 Mar 2012 16:18:43 GMT (envelope-from nobody) Message-Id: <201203231618.q2NGIhp4036716@red.freebsd.org> Date: Fri, 23 Mar 2012 16:18:43 GMT From: Christian Esken To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: misc/166340: Process under FreeBSD 9.0 hangs in uninterruptable sleep with apparently no syscall (empty wchan) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 16:20:12 -0000 >Number: 166340 >Category: misc >Synopsis: Process under FreeBSD 9.0 hangs in uninterruptable sleep with apparently no syscall (empty wchan) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 23 16:20:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Christian Esken >Release: FreeBSD 9.0 >Organization: >Environment: FreeBSD dev 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Thu Mar 1 17:17:19 CET 2012 root@dev:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I have a process that sometimes goes into uninterruptable sleep under FreeBSD 9.0. "ps" shows the process is in "D" state and wchan is "-". The process works reliably under various other operating systems, including misc FreeBSD 8 versions. I presume it should never happen that a process is in uninterruptible sleep without showing the kernel call in wchan. What could be the reason, or how can I further tackle the situation? The nature of the process is a remote logger. It reads access logs from a pipe/STDIN (Apache httpd CustomLog) and sends them via TCP to a "scribed" logging server. More details can be found on Stackoverflow [1]. Below is some more information, like "procstat -k" and uname output. --------------- This is the result from "procstat -k" and "procstat -kk" # procstat -k 38013 PID TID COMM TDNAME KSTACK 38013 100817 serelog - mi_switch sleepq_check_timeout sleepq_timedwait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall # procstat -kk 38013 PID TID COMM TDNAME KSTACK 38013 100817 serelog - mi_switch+0x174 sleepq_check_timeout+0x80 sleepq_timedwait_sig+0x20 _sleep+0x1b1 soreceive_generic+0xf95 kern_recvit+0x205 recvit+0x21 sys_recvfrom+0x82 amd64_syscall+0x450 Xfast_syscall+0xf7 --------------- uname -a: FreeBSD dev 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Thu Mar 1 17:17:19 CET 2012 root@dev:/usr/obj/usr/src/sys/GENERIC amd64 There is no NFS involved on the system. Best regards, Christian [1] http://stackoverflow.com/questions/9786501/process-under-freebsd-9-0-hangs-in-uninterruptable-sleep-with-apparently-no-sysc >How-To-Repeat: I can reproduce the issue quickly by sending a lot of HTTP requests. The problem does not occur when tracing the process with truss. If not solvable by just the description, I will isolate a small test case from the full source code. >Fix: >Release-Note: >Audit-Trail: >Unformatted: