From owner-freebsd-current@FreeBSD.ORG Mon Jun 24 22:22:17 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 958967FB; Mon, 24 Jun 2013 22:22:17 +0000 (UTC) (envelope-from sjk4015@gmail.com) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 70093129A; Mon, 24 Jun 2013 22:22:17 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id fa11so11646484pad.33 for ; Mon, 24 Jun 2013 15:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=+wsCrpzkgNK5Vtl2XywoNBeTZPSBAW/QyqujlghqyL4=; b=tf6vQDs5ZCKGE3Yfl41ldaT8PQ5s3cDiSzWsiiWCK9N0W40bsA1mrRYJmvMYSerbDm 62R8QQ+c4RnDhegJiZKVAG1IhI+FV4GTjEoK3y+Lp0LWPshDEzG10SXWaEf+A2plfNTy /boRPSGQQlbNlBW1Fkl3qSLMyZZ9gP5CSdkm+6+OfHTkUpdVVCVlfm8SD1tE0E3DXBU/ kdA8dtljiSicgfTunqg2610aBGqDy+UlPDVYpgBMLgXEwpGNgRyEmrmarhgbiwZd2lfW 3wGOMfKHCQ0Xn2Rr2fitnKD3Zvg8k5YSGFX+32Uhf6UTb9brqCgf31XjhP6L1/F9jwlh HZ/Q== MIME-Version: 1.0 X-Received: by 10.66.158.101 with SMTP id wt5mr28889815pab.8.1372112537258; Mon, 24 Jun 2013 15:22:17 -0700 (PDT) Sender: sjk4015@gmail.com Received: by 10.68.195.199 with HTTP; Mon, 24 Jun 2013 15:22:17 -0700 (PDT) Date: Mon, 24 Jun 2013 18:22:17 -0400 X-Google-Sender-Auth: sNNkqGIYV5qxYcToeDKZArLhzXM Message-ID: Subject: lock order reversal in r252098 From: Steven Kreuzer To: freebsd-arm@freebsd.org, current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 24 Jun 2013 22:22:17 -0000 Hello- I am running 10.0-CURRENT #0 r252098 on a beaglebone and I am getting the occasional LOR when reading/writing in an nfs mount lock order reversal: 1st 0xc1c0a150 newnfs (newnfs) @ /usr/src/sys/kern/vfs_syscalls.c:4064 2nd 0xc6a5e278 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2311 3rd 0xc1c12150 newnfs (newnfs) @ /usr/src/sys/kern/vfs_subr.c:2099 KDB: stack backtrace: end() at 0xd52035b0 scp=0xd52035b0 rlv=0xc05108e0 (db_trace_self+0x14) rsp=0xd5203498 rfp=0xc057394f Bad frame pointer: 0xc057394f Shortly after, the beaglebone locks up and requires a power cycle If anyone has any hints or can spare some cycles to help me debug this issue, please let me know Many Thanks