Re: Tmpfs panic in -current

From: Kevin Lo <kevlo_at_kevlo.org>
Date: Thu, 28 Jun 2012 16:25:12 +0800
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
Received on Thu Jun 28 2012 - 06:25:20 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:28 UTC