Date: Mon, 25 Jun 2012 12:55:48 +0300 From: Konstantin Belousov <kostikbel@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: <20120625095548.GD2337@deviant.kiev.zoral.com.ua> In-Reply-To: <1340589808.2192.1.camel@nsl> References: <1340589808.2192.1.camel@nsl>
next in thread | previous in thread | raw e-mail | index | archive | help
--T2hvUJ3zJitSqYsX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 >=20 > Does this look at all familiar to anyone? Can you look up the line corresponding to tmpfs_reg_resize + 0x627 address in your kernel ? The screenshot looks strange. The instruction on which the kernel trapped is int 0x28 which should not appear in the compiled code. --T2hvUJ3zJitSqYsX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/oNaQACgkQC3+MBN1Mb4jEoACguhbK+poJaPgsHk5VU5r6i6TK lhoAoNJir2lbjmIPOWnbpLrD06ggtfKj =arSr -----END PGP SIGNATURE----- --T2hvUJ3zJitSqYsX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120625095548.GD2337>