From owner-freebsd-current@FreeBSD.ORG Sat Feb 14 13:58:58 2004 Return-Path: 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 1391D16A4CE for ; Sat, 14 Feb 2004 13:58:58 -0800 (PST) Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with SMTP id F323543D1F for ; Sat, 14 Feb 2004 13:58:57 -0800 (PST) (envelope-from joseph@magnesium.net) Received: (qmail 77763 invoked by uid 1248); 14 Feb 2004 21:58:57 -0000 Date: 14 Feb 2004 15:58:57 -0600 Date: Sat, 14 Feb 2004 15:58:57 -0600 From: Joseph Dunn To: freebsd-current@freebsd.org Message-ID: <20040214215857.GA77673@toxic.magnesium.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Sun, 15 Feb 2004 05:04:42 -0800 Subject: Strange kernel debug output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 14 Feb 2004 21:58:58 -0000 Hi, I upgraded to -current last night from 5.1, and everything has been running smoothly. However, my kernel just spit this out: lock order reversal 1st 0xc29a6638 filedesc structure (filedesc structure) @ /usr/src/sys/kern/sys_ generic.c:901 2nd 0xc08710a0 Giant (Giant) @ /usr/src/sys/fs/specfs/spec_vnops.c:377 Stack backtrace: backtrace(0,ffffffff,c087e000,c087e028,c080da5c) at backtrace+0x12 witness_checkorder(c08710a0,9,c07aebdb,179) at witness_checkorder+0x593 _mtx_lock_flags(c08710a0,0,c07aebdb,179) at _mtx_lock_flags+0x67 spec_poll(cbd8aaf0,cbd8ab10,c06347e6,cbd8aaf0,c0853300) at spec_poll+0xe2 spec_vnoperate(cbd8aaf0) at spec_vnoperate+0x13 vn_poll(c2669088,40,c2a2bc80,c263dd20) at vn_poll+0x3a selscan(c263dd20,cbd8aba4,cbd8ab94,7,c08a0be0) at selscan+0xf1 kern_select(c263dd20,7,8069210,8069240,0) at kern_select+0x31d select(c263dd20,cbd8ad14,5,0,202) at select+0x45 syscall(2f,2f,2f,3,0) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (93), eip = 0x2829883b, esp = 0xbfbfe8fc, ebp = 0xbfbfe9a8 --- Is this something that I need to be worried about, or is it just debug information? Joseph Dunn