From owner-freebsd-net@FreeBSD.ORG Fri Aug 19 01:08:00 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96CCF106566B; Fri, 19 Aug 2011 01:08:00 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4E39E8FC0A; Fri, 19 Aug 2011 01:07:59 +0000 (UTC) Received: by qwc9 with SMTP id 9so2373146qwc.13 for ; Thu, 18 Aug 2011 18:07:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=PwVYXmBY3INaNeZnMHhD/TGtouPciscrJbGsm4wKSCk=; b=Nf2NhFyGWGxd6cuXzLLO32MBgEKklvshJfE6wlEF3GuoErU8Pw4YibGqc0iE1QURoe 1KOzR7bnSeyDAqP8AcCICKwVxZLj69NKFZxwoe0aNRdyvLKn8geeAxpsnYGmsrhFiMtX Ajf7dfNtLcK71+Qw3xO0lDKYxcds4KyfnJ9w0= MIME-Version: 1.0 Received: by 10.224.9.14 with SMTP id j14mr1285739qaj.129.1313716079523; Thu, 18 Aug 2011 18:07:59 -0700 (PDT) Received: by 10.224.178.65 with HTTP; Thu, 18 Aug 2011 18:07:59 -0700 (PDT) Date: Thu, 18 Aug 2011 18:07:59 -0700 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: LOR in route.c // scope6.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2011 01:08:00 -0000 Hi, I've periodically seen the following LOR when trying to repro a panic after restarting my network configuration: :lock order reversal: 1st 0xc4142f1c rtentry (rtentry) @ /usr/src/sys/net/routec:362 2nd 0xc3d08604 if_afdata (if_afdata) @ /usr/src/sys/netinet6/scope6.c:417 KDB: stack backtrace: db_trace_self_wrapper(...) _witness_debugger(...) _rw_wlock(...) in6_setscope(...) in6_purgeaddr(...) in6_control(...) ifioctl(...) soo_ioctl(...) kern_ioctl(...) ioctl(...) syscallenter(...) syscall(...) Xint0x80_syscall() I don't have a full backtrace or core for this. This was running r224948 UP with WITNESS. Thanks, -Garrett