Date: Thu, 16 Feb 2012 17:49:32 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: stable@freebsd.org Subject: Re: ZFS + nullfs + Linuxulator = panic? Message-ID: <20120216154932.GM3283@deviant.kiev.zoral.com.ua> In-Reply-To: <8F48D496-59BD-431D-B7F1-962A79C7ACC5@gromit.dlib.vt.edu> References: <CB455B5A-0583-4DFB-9712-6FFCC8B67AAB@gromit.dlib.vt.edu> <20120215004753.GQ3283@deviant.kiev.zoral.com.ua> <8F48D496-59BD-431D-B7F1-962A79C7ACC5@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--uOOcqLQ8l/YzXNYx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 16, 2012 at 10:09:27AM -0500, Paul Mather wrote: > On Feb 14, 2012, at 7:47 PM, Konstantin Belousov wrote: >=20 > > On Tue, Feb 14, 2012 at 09:38:18AM -0500, Paul Mather wrote: > >> I have a problem with RELENG_8 (FreeBSD/amd64 running a GENERIC kernel= , last built 2012-02-08). It will panic during the daily periodic scripts = that run at 3am. Here is the most recent panic message: > >>=20 > >> Fatal trap 9: general protection fault while in kernel mode > >> cpuid =3D 0; apic id =3D 00 > >> instruction pointer =3D 0x20:0xffffffff8069d266 > >> stack pointer =3D 0x28:0xffffff8094b90390 > >> frame pointer =3D 0x28:0xffffff8094b903a0 > >> code segment =3D base 0x0, limit 0xfffff, type 0x1b > >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 > >> processor eflags =3D resume, IOPL =3D 0 > >> current process =3D 72566 (ps) > >> trap number =3D 9 > >> panic: general protection fault > >> cpuid =3D 0 > >> KDB: stack backtrace: > >> #0 0xffffffff8062cf8e at kdb_backtrace+0x5e > >> #1 0xffffffff805facd3 at panic+0x183 > >> #2 0xffffffff808e6c20 at trap_fatal+0x290 > >> #3 0xffffffff808e715a at trap+0x10a > >> #4 0xffffffff808cec64 at calltrap+0x8 > >> #5 0xffffffff805ee034 at fill_kinfo_thread+0x54 > >> #6 0xffffffff805eee76 at fill_kinfo_proc+0x586 > >> #7 0xffffffff805f22b8 at sysctl_out_proc+0x48 > >> #8 0xffffffff805f26c8 at sysctl_kern_proc+0x278 > >> #9 0xffffffff8060473f at sysctl_root+0x14f > >> #10 0xffffffff80604a2a at userland_sysctl+0x14a > >> #11 0xffffffff80604f1a at __sysctl+0xaa > >> #12 0xffffffff808e62d4 at amd64_syscall+0x1f4 > >> #13 0xffffffff808cef5c at Xfast_syscall+0xfc > >=20 > > Please look up the line number for the fill_kinfo_thread+0x54. >=20 >=20 > Is there a way for me to do this from the above information? As > I said in the original message, I failed to get a crash dump after > reboot (because, it turns out, I hadn't set up my gmirror swap device > properly). Alas, with the latest panic, it appears to have hung[1] > during the "Dumping" phase, so it looks like I won't get a saved crash > dump this time, either. :-( Load the kernel.debug into kgdb, and from there do "list *fill_kinfo_thread+0x54". --uOOcqLQ8l/YzXNYx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk89JYsACgkQC3+MBN1Mb4jTHQCgqgF5VyownHPJywbHEphRblMH NFoAoNpHWh5b61G9IcxuNpaDzxI7dqQr =7Vbm -----END PGP SIGNATURE----- --uOOcqLQ8l/YzXNYx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120216154932.GM3283>