Date: Thu, 16 Feb 2012 10:09:27 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Konstantin Belousov <kostikbel@gmail.com> Cc: stable@freebsd.org Subject: Re: ZFS + nullfs + Linuxulator = panic? Message-ID: <8F48D496-59BD-431D-B7F1-962A79C7ACC5@gromit.dlib.vt.edu> In-Reply-To: <20120215004753.GQ3283@deviant.kiev.zoral.com.ua> References: <CB455B5A-0583-4DFB-9712-6FFCC8B67AAB@gromit.dlib.vt.edu> <20120215004753.GQ3283@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 14, 2012, at 7:47 PM, Konstantin Belousov wrote:
> 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.
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. :-(
Speaking of the latest panic, here it is:
Fatal trap 12: page fault while in kernel mode
cpuid =3D 0; apic id =3D 00
fault virtual address =3D 0x308
fault code =3D supervisor read data, page not present
instruction pointer =3D 0x20:0xffffffff806026ef
stack pointer =3D 0x28:0xffffff8094acd2d0
frame pointer =3D 0x28:0xffffff8094acd350
code segment =3D base 0x0, limit 0xfffff, type 0x1b
=3D DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags =3D interrupt enabled, resume, IOPL =3D 0
current process =3D 20992 (df)
trap number =3D 12
panic: page 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 0xffffffff808e6f71 at trap_pfault+0x201
#4 0xffffffff808e742f at trap+0x3df
#5 0xffffffff808cec64 at calltrap+0x8
#6 0xffffffff80602e1e at _sx_xlock+0x4e
#7 0xffffffff80f9ca35 at rrw_enter+0xa5
#8 0xffffffff80f9ce86 at zfs_statfs+0x46
#9 0xffffffff80681258 at __vfs_statfs+0x28
#10 0xffffffff81476521 at nullfs_statfs+0x51
#11 0xffffffff80681258 at __vfs_statfs+0x28
#12 0xffffffff80690b22 at kern_statfs+0x1b2
#13 0xffffffff80690c77 at statfs+0x37
#14 0xffffffff808e62d4 at amd64_syscall+0x1f4
#15 0xffffffff808cef5c at Xfast_syscall+0xfc
Cheers,
Paul.
[1] Not quite hung solid: when I press the power button I get this =
appearing on the console:
acpi0: suspend request ignored (not ready yet)
acpi0: request to enter state S5 failed (err 6)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8F48D496-59BD-431D-B7F1-962A79C7ACC5>