From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 21:13:37 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D70CDF6 for ; Mon, 23 Jun 2014 21:13:37 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC9B72511 for ; Mon, 23 Jun 2014 21:13:36 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F23F3B945; Mon, 23 Jun 2014 17:13:35 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: panic: privileged instruction fault Date: Mon, 23 Jun 2014 16:41:07 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <538D908F.6050801@rixtel.com> In-Reply-To: <538D908F.6050801@rixtel.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201406231641.07691.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 23 Jun 2014 17:13:36 -0400 (EDT) Cc: Ilmars =?utf-8?q?Knip=C5=A1is?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 21:13:37 -0000 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) 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