From owner-freebsd-threads@freebsd.org Mon Apr 4 13:04:11 2016 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 701F8B022F2 for ; Mon, 4 Apr 2016 13:04:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60BD910A3 for ; Mon, 4 Apr 2016 13:04:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u34D4AO3060502 for ; Mon, 4 Apr 2016 13:04:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Mon, 04 Apr 2016 13:04:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 13:04:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #88 from Robert Blayzor --- Just a follow-up on this. The last patch has been running for a few days and I've not had an unexpected crash yet. I'm not saying it won't happen, it's = not unusual for us not to see this for several days; then suddenly we may start getting them at a rate of 1+ per day. Just following up as we continue to monitor this... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Wed Apr 6 18:30:26 2016 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EE15B06737 for ; Wed, 6 Apr 2016 18:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0C61CE7 for ; Wed, 6 Apr 2016 18:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u36IUPj8025276 for ; Wed, 6 Apr 2016 18:30:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Wed, 06 Apr 2016 18:30:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 18:30:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #89 from Robert Blayzor --- Not sure this related or part of the problem, but the first time I've seen = this on any of the VM's kernel messages... lock order reversal: 1st 0xfffff80009d9e240 ufs (ufs) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/kern/vfs_subr.c:2253 2nd 0xfffffe007c5bef50 bufwait (bufwait) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/ufs/ffs/ffs_vnops.c:262 3rd 0xfffff800117edd50 ufs (ufs) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/kern/vfs_subr.c:2253 KDB: stack backtrace: #0 0xffffffff80484260 at kdb_backtrace+0x60 #1 0xffffffff804a30d4 at witness_checkorder+0xe24 #2 0xffffffff8042b98a at __lockmgr_args+0x9ea #3 0xffffffff806818f4 at ffs_lock+0x84 #4 0xffffffff8073dc2c at VOP_LOCK1_APV+0xfc #5 0xffffffff805057da at _vn_lock+0xaa #6 0xffffffff804f6de7 at vget+0x67 #7 0xffffffff804ea601 at vfs_hash_get+0xe1 #8 0xffffffff8067cf00 at ffs_vgetf+0x40 #9 0xffffffff80674bf0 at softdep_sync_buf+0xac0 #10 0xffffffff80682656 at ffs_syncvnode+0x286 #11 0xffffffff80659a5e at ffs_truncate+0x6ae #12 0xffffffff8068987a at ufs_direnter+0x81a #13 0xffffffff806926a5 at ufs_makeinode+0x575 #14 0xffffffff8068e58d at ufs_create+0x2d #15 0xffffffff8073b5c1 at VOP_CREATE_APV+0xf1 #16 0xffffffff80504e93 at vn_open_cred+0x2c3 #17 0xffffffff804fdf8f at kern_openat+0x26f --=20 You are receiving this mail because: You are the assignee for the bug.=