From owner-freebsd-current@FreeBSD.ORG Thu Aug 4 06:36:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D44116A41F for ; Thu, 4 Aug 2005 06:36:38 +0000 (GMT) (envelope-from tyler@tamu.edu) Received: from smtp-relay.tamu.edu (smtp-relay.tamu.edu [165.91.143.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A281443D46 for ; Thu, 4 Aug 2005 06:36:37 +0000 (GMT) (envelope-from tyler@tamu.edu) Received: from [165.91.46.38] (tamulink-0038.vpn.tamu.edu [165.91.46.38]) by smtp-relay.tamu.edu (8.13.3/8.13.3) with ESMTP id j746aVh2051190 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Thu, 4 Aug 2005 01:36:36 -0500 (CDT) (envelope-from tyler@tamu.edu) Mime-Version: 1.0 (Apple Message framework v733) Content-Transfer-Encoding: 7bit Message-Id: <2C087707-319D-44BE-B770-89B7AF3CBD96@tamu.edu> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: "R. Tyler Ballance" Date: Thu, 4 Aug 2005 01:36:40 -0500 X-Mailer: Apple Mail (2.733) Received-SPF: none (smtp-relay.tamu.edu: domain of tyler@tamu.edu does not designate permitted sender hosts) Subject: Kernel spewing errors/warnings on 7.0-CURRENT 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: Thu, 04 Aug 2005 06:36:38 -0000 After restarting my FreeBSD-CURRENT workstation, shortly after I logged in, and shortly before bg_fsck had completely (power outage last night) I got the following set of messages spewed to ttyv0 : Aug 3 16:19:17 workstation kernel: lock order reversal Aug 3 16:19:17 workstation kernel: 1st 0xc097ab20 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1491 Aug 3 16:19:17 workstation kernel: 2nd 0xc1060144 system map (system map) @ /usr/src/sys/vm/vm_map.c:2317 Aug 3 16:19:17 workstation kernel: KDB: stack backtrace: Aug 3 16:19:17 workstation kernel: kdb_backtrace (0,ffffffff,c092fc38,c092fd78,c08ba624) at kdb_backtrace+0x29 Aug 3 16:19:17 workstation kernel: witness_checkorder (c1060144,9,c0870d80,90d) at witness_checkorder+0x564 Aug 3 16:19:17 workstation kernel: _mtx_lock_flags (c1060144,0,c0870d80,90d) at _mtx_lock_flags+0x5b Aug 3 16:19:17 workstation kernel: _vm_map_lock (c10600c0,c0870d80,90d) at _vm_map_lock+0x26 Aug 3 16:19:17 workstation kernel: vm_map_remove (c10600c0,c1d0a000,c1d0b000,d56ecc08,c077e4e1) at vm_map_remove+0x1f Aug 3 16:19:17 workstation kernel: kmem_free (c10600c0,c1d0a000,1000,d56ecc38,c077de8e) at kmem_free+0x25 Aug 3 16:19:17 workstation kernel: page_free(c1d0a000,1000,2) at page_free+0x29 Aug 3 16:19:17 workstation kernel: zone_drain(c104a960) at zone_drain +0x26a Aug 3 16:19:17 workstation kernel: zone_foreach (c077dc24,d56eccec,c078fcaf,c1a3d900,d56ecc74) at zone_foreach+0x37 Aug 3 16:19:17 workstation kernel: uma_reclaim (c1a3d900,d56ecc74,0,c0926260,d56ecc80) at uma_reclaim+0x12 Aug 3 16:19:17 workstation kernel: vm_pageout_scan (0,c097af80,0,c087226d,5c3) at vm_pageout_scan+0x103 Aug 3 16:19:17 workstation kernel: vm_pageout (0,d56ecd38,0,c0790a68,0) at vm_pageout+0x2c3 Aug 3 16:19:17 workstation kernel: fork_exit(c0790a68,0,d56ecd38) at fork_exit+0xa0 Aug 3 16:19:17 workstation kernel: fork_trampoline() at fork_trampoline+0x8 Aug 3 16:19:17 workstation kernel: --- trap 0x1, eip = 0, esp = 0xd56ecd6c, ebp = 0 --- FreeBSD workstation.local 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sat Jul 16 15:09:18 CDT 2005 root@workstation.local:/usr/obj/usr/src/sys/ GENERIC i386 ***************************** This didn't cause the kernel to panic or anything, I just figured the kernel debugger output might be helpful to somebody here... The same lock order reversal happened the last time I did a clean reboot, and this time after a hard restart. dmesg output is here if needed: http://agentdero.com/~tyler/ dmesg.workstation.txt Is this nothing to worry about? Or is something going slightly wrong? Cheers, -R. Tyler Ballance