From owner-freebsd-fs@FreeBSD.ORG Thu Jun 28 08:25:20 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F3DA1065674; Thu, 28 Jun 2012 08:25:20 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id CA9EB8FC1C; Thu, 28 Jun 2012 08:25:19 +0000 (UTC) Received: from [127.0.0.1] (git.kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.5/8.14.5) with ESMTP id q5S8P5N8079387; Thu, 28 Jun 2012 16:25:06 +0800 (CST) (envelope-from kevlo@kevlo.org) Message-ID: <1340871912.2151.9.camel@nsl> From: Kevin Lo To: Gleb Kurtsou Date: Thu, 28 Jun 2012 16:25:12 +0800 In-Reply-To: <20120628070948.GA1197@reks> References: <1340589808.2192.1.camel@nsl> <20120625095548.GD2337@deviant.kiev.zoral.com.ua> <1340685505.2170.5.camel@nsl> <20120626102424.GL2337@deviant.kiev.zoral.com.ua> <1340763363.2147.1.camel@nsl> <1340774954.2147.3.camel@nsl> <20120628070948.GA1197@reks> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Cc: freebsd-fs@freebsd.org, freebsd-current Subject: Re: Tmpfs panic in -current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2012 08:25:20 -0000 On 四, 2012-06-28 at 10:09 +0300, Gleb Kurtsou wrote: > On (27/06/2012 13:29), Kevin Lo wrote: > > Kevin Lo wrote: > > > Konstantin Belousov wrote: > > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > > > Konstantin Belousov wrote: > > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > > > > > I've observed a panic in recent -current several times but I only > > > > > > > have a picture of the backtrace: > > > > > > > http://people.freebsd.org/~kevlo/panic_tmpfs.jpg > > > > > > > > > > > > > > Does this look at all familiar to anyone? > > > > > > > > > > > > Can you look up the line corresponding to tmpfs_reg_resize + 0x627 address > > > > > > in your kernel ? > > > > > > > > > > Sure. > > > > > > > > > > > The screenshot looks strange. The instruction on which the kernel trapped > > > > > > is int 0x28 which should not appear in the compiled code. > > Kevin, do you have fuse modules loaded? It looks much like memmory > corruption issue. No, I don't have that module loaded. # kldstat Id Refs Address Size Name 1 14 0xc0400000 bab9e8 kernel 2 1 0xc0fac000 1d58 msdosfs_iconv.ko 3 2 0xc0fae000 67a8 libiconv.ko 4 1 0xc728e000 9000 tmpfs.ko 5 1 0xc789b000 4000 uhid.ko