From owner-freebsd-bugs Mon Sep 10 2: 0:10 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4E03537B40A for ; Mon, 10 Sep 2001 02:00:01 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8A901S52896; Mon, 10 Sep 2001 02:00:01 -0700 (PDT) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0097937B401 for ; Mon, 10 Sep 2001 01:55:39 -0700 (PDT) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8A8tc352141; Mon, 10 Sep 2001 01:55:38 -0700 (PDT) (envelope-from nobody) Message-Id: <200109100855.f8A8tc352141@freefall.freebsd.org> Date: Mon, 10 Sep 2001 01:55:38 -0700 (PDT) From: Ville-Pertti Keinonen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/30482: calcru calls printf while holding a spin lock Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 30482 >Category: kern >Synopsis: calcru calls printf while holding a spin lock >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Sep 10 02:00:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Ville-Pertti Keinonen >Release: 5.0-current >Organization: >Environment: >Description: A machine that previously frequently reported problems with microuptime() going backwards in calcru started crashing after a recent update. I'm just guessing based on the stack trace and the panic message (and this is the first time I look at anything related to SMPng locking), but it seems that calcru calls printf which eventually tries to wake up another process and grab allproc_lock while sched_lock is held... This seems like an obvious enough bug that it should not require further details. >How-To-Repeat: >Fix: Remove or defer the printf-calls. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message