From owner-freebsd-current@FreeBSD.ORG Sun Dec 18 03:41:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77A94106566B for ; Sun, 18 Dec 2011 03:41:16 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4FDF78FC0A for ; Sun, 18 Dec 2011 03:41:16 +0000 (UTC) Received: by dakp5 with SMTP id p5so4375643dak.13 for ; Sat, 17 Dec 2011 19:41:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1j5oa1/cEIgg1krGUAxzfzj2PNUUu2C3o6A40AsGykw=; b=Icpq6C/gXrsOpM2YdjJc0vBh5BYy8fOr8kzcktLXqz0Dzdcv0rbHtkc5A0lMJH9Djd KEdSPw3AhROK6UBD1QFaxK8TqRQfkPIsDfQ0uTdsDSuxOQCuLtZfugP5BBZKfmVFwhyK WvHjPfHh1OnlZ/gdDu25mltTq5qFHZL+BoXns= MIME-Version: 1.0 Received: by 10.68.73.228 with SMTP id o4mr28661869pbv.34.1324179675860; Sat, 17 Dec 2011 19:41:15 -0800 (PST) Sender: mdf356@gmail.com Received: by 10.68.197.198 with HTTP; Sat, 17 Dec 2011 19:41:15 -0800 (PST) In-Reply-To: <20111217204514.2fa77ea2@kan.dyndns.org> References: <4EED2F1C.2060409@zedat.fu-berlin.de> <20111217204514.2fa77ea2@kan.dyndns.org> Date: Sat, 17 Dec 2011 19:41:15 -0800 X-Google-Sender-Auth: 57i0k8WaMRG2uikcDWIZj0Ta42s Message-ID: From: mdf@FreeBSD.org To: Alexander Kabaev Content-Type: text/plain; charset=ISO-8859-1 Cc: Current FreeBSD , "O. Hartmann" Subject: Re: Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 03:41:16 -0000 On Sat, Dec 17, 2011 at 5:45 PM, Alexander Kabaev wrote: > On Sun, 18 Dec 2011 01:09:00 +0100 > "O. Hartmann" wrote: > >> Sleeping thread (tid 100033, pid 16) owns a non sleepable lock >> panic: sleeping thread >> cpuid = 0 >> >> PID 16 is always USB on my box. > > You really need to give us a backtrace when you quote panics. It is > impossible to make any sense of the above panic message without more > context. In the case of this panic, the stack of the thread which panics is useless; it's someone trying to propagate priority that discovered it. A backtrace on tid 100033 would be useful. With WITNESS enabled, it's possible to have this panic display the stack of the incorrectly sleeping thread at the time it acquired the lock, as well, but this code isn't in CURRENT or any release. I have a patch at $WORK I can dig up on Monday. Cheers, matthew