Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Jun 2012 10:09:48 +0300
From:      Gleb Kurtsou <gleb.kurtsou@gmail.com>
To:        Kevin Lo <kevlo@kevlo.org>
Cc:        freebsd-fs@freebsd.org, freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: Tmpfs panic in -current
Message-ID:  <20120628070948.GA1197@reks>
In-Reply-To: <1340774954.2147.3.camel@nsl>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120628070948.GA1197>