From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 7 05:10:02 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 44EBD6B7 for ; Thu, 7 Mar 2013 05:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 35A6AF22 for ; Thu, 7 Mar 2013 05:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r275A1Jq077856 for ; Thu, 7 Mar 2013 05:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r275A1ju077855; Thu, 7 Mar 2013 05:10:01 GMT (envelope-from gnats) Date: Thu, 7 Mar 2013 05:10:01 GMT Message-Id: <201303070510.r275A1ju077855@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Rasmus Skaarup Subject: Re: kern/176636: Periodical crashes with 9.1-R X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Rasmus Skaarup List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2013 05:10:02 -0000 The following reply was made to PR kern/176636; it has been noted by GNATS. From: Rasmus Skaarup To: Andriy Gapon Cc: bug-followup@FreeBSD.org Subject: Re: kern/176636: Periodical crashes with 9.1-R Date: Thu, 7 Mar 2013 06:00:46 +0100 This is the only kind of panic I get - after your patch: Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x60 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff8162e4f0 stack pointer =3D 0x28:0xffffff81624726e0 frame pointer =3D 0x28:0xffffff81624727d0 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 26068 (zpool) trap number =3D 12 panic: page fault cpuid =3D 1 KDB: stack backtrace: #0 0xffffffff809208a6 at kdb_backtrace+0x66 #1 0xffffffff808ea8be at panic+0x1ce #2 0xffffffff80bd8240 at trap_fatal+0x290 #3 0xffffffff80bd857d at trap_pfault+0x1ed #4 0xffffffff80bd8b9e at trap+0x3ce #5 0xffffffff80bc315f at calltrap+0x8 #6 0xffffffff81673975 at sa_handle_get_from_db+0x95 #7 0xffffffff81673a38 at sa_handle_get+0x48 #8 0xffffffff8169f516 at zfs_grab_sa_handle+0x96 #9 0xffffffff8169faca at zfs_obj_to_path+0x6a #10 0xffffffff816b8c75 at zfs_ioc_obj_to_path+0x75 #11 0xffffffff816bad46 at zfsdev_ioctl+0xe6 #12 0xffffffff807db28b at devfs_ioctl_f+0x7b #13 0xffffffff80932325 at kern_ioctl+0x115 #14 0xffffffff8093255d at sys_ioctl+0xfd #15 0xffffffff80bd7ae6 at amd64_syscall+0x546 #16 0xffffffff80bc3447 at Xfast_syscall+0xf7 Br Rasmus On 06/03/2013, at 16.22, Rasmus Skaarup wrote: >=20 > Tonight I will migrate all data to a UFS drive and let it run for a = few days. If it works, I will create a new ZFS pool and move data back = and see what happens. >=20 > Is there any information you need before I proceed? >=20 > Br > Rasmus Skaarup