From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 22:51:19 2008 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 0598D106567D for ; Fri, 6 Jun 2008 22:51:18 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id DC3C98FC35 for ; Fri, 6 Jun 2008 22:51:18 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1676502rvf.43 for ; Fri, 06 Jun 2008 15:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=sd0aoxSEJaEJJ6doPxaDNlHYW0YETYEZfDU1DlYfVb0=; b=DNR87QNyF+nx+96bxmEh1S6KLd6bcG8snyn2T+hgwfxGR8IdGPHMaiPoWqeLqc6VMq AThQNXiYFNu/ZRTPgsHZSl0JlICrGduwv5GK2euBJfCuQUThO03K6k3knW58/BLhQGin NAut6q9RFg2F2wB3GlVuyaM/eSTLjQbNgU6mQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=KqjCtkyZIddh6QB6D7gk/sxuTWLnU/tBjlYMplLJtBe0t0Bpn9jQuO3i8pbK+/RFa9 1dyX0vQriW0LrW1Pmtvnk8AoG44P2QXt+k6RnVmlPhPMkXJ1wk9mdAoERD89yQZl2SRy 0IMa2uRL5yrjiN30vPuiZGcxC7GrQORRGCm/k= Received: by 10.140.134.15 with SMTP id h15mr412994rvd.65.1212790958770; Fri, 06 Jun 2008 15:22:38 -0700 (PDT) Received: by 10.140.248.15 with HTTP; Fri, 6 Jun 2008 15:22:38 -0700 (PDT) Message-ID: <54db43990806061522v3db7b075mb563a16a123efa63@mail.gmail.com> Date: Fri, 6 Jun 2008 18:22:38 -0400 From: "Bob Johnson" To: "Gardner Bell" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-current@freebsd.org Subject: Re: calcru: runtime went backwards (and lock order reversal) 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: Fri, 06 Jun 2008 22:51:19 -0000 On 6/6/08, Gardner Bell wrote: > Hello, > > I'm seeing the following printed on my screen after my system became > unresponsive while background fsck was running for ~10 mins or so. > Previous to this, my machine crashed after a power outage in my > neighborhood. > > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.0-CURRENT #0: Wed May 28 10:43:47 EDT 2008 > root@home:/usr/obj/usr/src/sys/TYAN > > lock order reversal: > 1st 0xffffff0001282430 snaplk (snaplk) @ > /usr/src/sys/kern/vfs_vnops.c:292 > 2nd 0xffffff0001750270 ufs (ufs) @ > /usr/src/sys/ufs/ffs/ffs_snapshot.c:1578 I'd guess the lock order reversal is more significant than the "runtime went backwards" messages. See http://gireeshdn.blogspot.com/2006/12/lock-order-reversals-courtesy-freebsd.html for more information about what it indicates. > KDB: stack backtrace: [...] > calcru: runtime went backwards from 33275 usec to 290 usec for pid 999 > (csh) > calcru: runtime went backwards from 469322 usec to 3929 usec for pid > 999 (csh) > calcru: runtime went backwards from 13323 usec to 109 usec for pid 998 > (su) [...etc.] The "runtime went backwards" errors are common and probably indicate a problem servicing interrupts, either because of a driver problem or a hardware problem. For example, on some motherboards, the Intel SpeedStep implementation is buggy and can cause this error. Often, changing the method used to update the system clock will solve the problem. A Google search will give you lots of suggestions. - Bob