From owner-freebsd-current@FreeBSD.ORG Fri Jan 18 20:50:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 80B19789 for ; Fri, 18 Jan 2013 20:50:31 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 0CA9572E for ; Fri, 18 Jan 2013 20:50:30 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id z53so1106767wey.34 for ; Fri, 18 Jan 2013 12:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/gs/YLaIFIp25J1hb/Wh5fsLfcU+AegCZmV4YdYpT7g=; b=huBreQnSUpnlD5BPQR76ZyjUHMezSLWG++mapsZT5Qzc/3s929SsIkopX4bVuCpGq1 WxrTGKQdq4GnCiGLefWz9sMp3Gn10R+USxVTnpfSwty3GCDFR6ZLLx5JMEAqr1pY8vRG o5WaDJ51M32RRDNM9JL0V3E4zJnlHWJVSZTvj7pAIfYkXQtivxv665UefLyUkAy5GZ3B jbnBAC21wgDkDM8QCur5Ig3s0vabIpVck3fX8wnYiIXltMAyS7gVtXtNPkAtz7ZRiHny Hs/7tJVBW5QGYocM0XwDnrw33g4O1ypp7qrD5yEZUtTdOEeXsHY9TjQ8OxVb7TYzf/ZJ RRBw== MIME-Version: 1.0 X-Received: by 10.180.101.99 with SMTP id ff3mr5680339wib.21.1358542230257; Fri, 18 Jan 2013 12:50:30 -0800 (PST) Received: by 10.216.100.194 with HTTP; Fri, 18 Jan 2013 12:50:30 -0800 (PST) In-Reply-To: <50EF3FEC.60605@delphij.net> References: <50EB602F.9050300@delphij.net> <20130108000233.GZ82219@kib.kiev.ua> <50EB63A9.50903@delphij.net> <50EB870D.3020306@delphij.net> <50EF3FEC.60605@delphij.net> Date: Fri, 18 Jan 2013 14:50:30 -0600 Message-ID: Subject: Re: sysctl -a causes kernel trap 12 From: Brandon Gooch To: d@delphij.net Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Konstantin Belousov , freebsd-current@freebsd.org 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: Fri, 18 Jan 2013 20:50:31 -0000 On Thu, Jan 10, 2013 at 4:25 PM, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > To all: this became more and more hard to replicate lately. I've > tried these options and the most important progress is that it's > possible to get a crashdump when debug.debugger_on_panic=0 and I > managed to get a backtrace which indicates the panic occur when trying > to do mtx_lock(&Giant) -> __mtx_lock_sleep -> turnstile_wait -> > propagate_priority, but after I've added some instruments to the > surrounding code and enabled INVARIANT and/or WITNESS, it mysteriously > went away. > > Reverting my instruments code and update to latest svn makes the issue > disappear for one day. I've hit it again today but unfortunately > didn't get a successful dump and after reboot I can't reproduce it > again :( > > Still trying... > Any updates Xin? I was actually hitting what I believe to be exactly the same issue as you on one of my systems, and, as you've seen, adding any extra debugging or diagnostics seemed to eliminate the issue. I was able to generate quite a few vmcores and still have these sitting around in my filesystem (along with the kernels that helped produce them). I can recreate this crash on my system by compiling the NVIDIA driver with clang at -01 and above. Although it's been noted that this issue has been seen in scenarios without an NIVIDIA driver in the mix, whatever is happening in the kernel to cause the panic is somehow triggered by this, at least on my system. -Brandon