Date: Mon, 23 Jun 2014 16:41:07 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Ilmars =?utf-8?q?Knip=C5=A1is?= <ilmars.knipshis@rixtel.com> Subject: Re: panic: privileged instruction fault Message-ID: <201406231641.07691.jhb@freebsd.org> In-Reply-To: <538D908F.6050801@rixtel.com> References: <538D908F.6050801@rixtel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, June 03, 2014 5:08:31 am Ilmars Knip=C5=A1is wrote: > Hello! >=20 > This is binary install of FreeBSD 10 on Intel server board S1200 V3 RP=20 > with ZFS mirrored SSD disks for OS and ZFS RAID 10 with 4 HDD disks for=20 > data. >=20 > I am getting the kernel panic at random time almost every day: > panic: privileged instruction fault > panic: general protection fault > panic: vm_fault: fault on nofault entry, addr: fffffe046667d000 > panic: page fault >=20 > Could it be faulty RAM ? >=20 >=20 >=20 > Small extract from core.txt: >=20 > FreeBSD xx.xxx.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan= =20 > 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC = =20 > amd64 >=20 > Unread portion of the kernel message buffer: > trap number =3D 1 > panic: privileged instruction fault > cpuid =3D 0 > KDB: stack backtrace: > #0 0xffffffff808e7dd0 at kdb_backtrace+0x60 > #1 0xffffffff808af8b5 at panic+0x155 > #2 0xffffffff80c8e692 at trap_fatal+0x3a2 > #3 0xffffffff80c8e2cf at trap+0x7bf > #4 0xffffffff80c75392 at calltrap+0x8 > #5 0xffffffff81853b3d at spa_sync+0x61d > #6 0xffffffff8185c925 at txg_sync_thread+0x375 > #7 0xffffffff8088198a at fork_exit+0x9a > #8 0xffffffff80c758ce at fork_trampoline+0xe > Uptime: 13h55m6s > Dumping 1059 out of 16299=20 > MB:..2%..11%..22%..31%..41%..52%..61%..71%..81%..91% >=20 > Reading symbols from /boot/kernel/zfs.ko.symbols...done. > Loaded symbols for /boot/kernel/zfs.ko.symbols > Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. > Loaded symbols for /boot/kernel/opensolaris.ko.symbols > Reading symbols from /boot/kernel/ums.ko.symbols...done. > Loaded symbols for /boot/kernel/ums.ko.symbols > Reading symbols from /boot/kernel/pflog.ko.symbols...done. > Loaded symbols for /boot/kernel/pflog.ko.symbols > Reading symbols from /boot/kernel/pf.ko.symbols...done. > Loaded symbols for /boot/kernel/pf.ko.symbols > Reading symbols from /boot/kernel/nullfs.ko.symbols...done. > Loaded symbols for /boot/kernel/nullfs.ko.symbols > Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. > Loaded symbols for /boot/kernel/fdescfs.ko.symbols > #0 doadump (textdump=3D<value optimized out>) at pcpu.h:219 > 219 pcpu.h: No such file or directory. > in pcpu.h Can you do 'x/i 0xffffffff81853b3d' in kgdb? (Yes, it is quite possible th= is=20 is due to bad RAM) =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406231641.07691.jhb>