Date: Mon, 30 Jun 2014 13:50:20 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Ilmars =?utf-8?q?Knip=C5=A1is?= <ilmarsk@rixbox.com> Subject: Re: panic: privileged instruction fault Message-ID: <201406301350.20417.jhb@freebsd.org> In-Reply-To: <53AA760E.4020202@rixbox.com> References: <538D908F.6050801@rixtel.com> <201406231641.07691.jhb@freebsd.org> <53AA760E.4020202@rixbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, June 25, 2014 3:11:10 am Ilmars Knip=C5=A1is wrote: > On 2014.06.23. 23:41, John Baldwin wrote: > > On Tuesday, June 03, 2014 5:08:31 am Ilmars Knip=C5=A1is wrote: > >> Hello! > >> > >> This is binary install of FreeBSD 10 on Intel server board S1200 V3 RP > >> with ZFS mirrored SSD disks for OS and ZFS RAID 10 with 4 HDD disks for > >> data. > >> > >> 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 > >> > >> Could it be faulty RAM ? > >> > >> > >> > >> Small extract from core.txt: > >> > >> FreeBSD xx.xxx.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu J= an > >> 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC > >> amd64 > >> > >> 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 > >> MB:..2%..11%..22%..31%..41%..52%..61%..71%..81%..91% > >> > >> 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 possibl= e=20 this > > is due to bad RAM) > > > I am not familiar with kgdb. Is that exactly syntax to use? Yes. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406301350.20417.jhb>