From owner-freebsd-current Sat Feb 1 12:19:47 2003 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 EE76037B401 for ; Sat, 1 Feb 2003 12:19:46 -0800 (PST) Received: from mail.rpi.edu (mail.rpi.edu [128.113.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BD0443F43 for ; Sat, 1 Feb 2003 12:19:46 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id h11KJdcm281620 for ; Sat, 1 Feb 2003 15:19:39 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Sat, 1 Feb 2003 15:19:37 -0500 To: current@FreeBSD.org From: Garance A Drosihn Subject: LockOrderReversal in current Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From time-to-time I notice people reporting lock-order-reversal messages here. My system popped up with one sometime overnight, I have no idea what it might have been doing at the time. lock order reversal 1st 0xc0514fc0 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151 2nd 0xc410707c radix node head (radix node head) @ /usr/src/sys/net/route.c:549 This is on a dual-CPU system. Current-branch as built on Jan 27th. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message