From owner-freebsd-stable@freebsd.org Wed Oct 14 14:42:24 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EAFDA1396E for ; Wed, 14 Oct 2015 14:42:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 1CE11231 for ; Wed, 14 Oct 2015 14:42:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t9EEgIP2002165 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Oct 2015 17:42:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t9EEgIP2002165 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t9EEgHTW002164; Wed, 14 Oct 2015 17:42:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 Oct 2015 17:42:17 +0300 From: Konstantin Belousov To: Frank Razenberg Cc: freebsd-stable@freebsd.org Subject: Re: 10.2-STABLE amd64 panic: page fault while in kernel mode Message-ID: <20151014144217.GV2257@kib.kiev.ua> References: <561E5E2F.90404@zzattack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <561E5E2F.90404@zzattack.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 14:42:24 -0000 On Wed, Oct 14, 2015 at 03:52:47PM +0200, Frank Razenberg wrote: > After upgrading from 9.2 to 10.1 I first started noticing panics. They > occurred roughly weekly and since this storage machine isn't frequently > used I didn't look into it much further. After updating for 10.2-STABLE > the panics have gone from weekly to daily. > The machine has 32GB of non-registered ECC DDR3-1066 RAM. There's also a > 10-disk raidz2 pool. I've ran memtest86+ for 72 hours straight with no > errors. > > Crash dumps all feature the following: > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 12 > fault virtual address = 0x1d1c0bec0 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff804fda65 > stack pointer = 0x28:0xfffffe0698f21870 > frame pointer = 0x28:0xfffffe0698f218d0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 6106 (pickup) > trap number = 12 > panic: page fault > cpuid = 2 > > > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:219 > #1 0xffffffff8053ce32 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:455 > #2 0xffffffff8053d215 in vpanic (fmt=, ap= optimized out>) at /usr/src/sys/kern/kern_shutdown.c:762 > #3 0xffffffff8053d0a3 in panic (fmt=0x0) at > /usr/src/sys/kern/kern_shutdown.c:691 > #4 0xffffffff807755db in trap_fatal (frame=, > eva=) at /usr/src/sys/amd64/amd64/trap.c:851 > #5 0xffffffff807758dd in trap_pfault (frame=0xfffffe0698dbc7c0, > usermode=) at /usr/src/sys/amd64/amd64/trap.c:674 > #6 0xffffffff80774f7a in trap (frame=0xfffffe0698dbc7c0) at > /usr/src/sys/amd64/amd64/trap.c:440 > #7 0xffffffff8075b0f2 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:236 > #8 0xffffffff804fda65 in kqueue_close (fp=0xfffff803e4967190, > td=0xfffff80014b094a0) at /usr/src/sys/kern/kern_event.c:1750 > #9 0xffffffff804f25f9 in _fdrop (fp=0xfffff803e4967190, > td=0xfffff802b5d2a000) at file.h:343 > #10 0xffffffff804f4e9e in closef (fp=, td= optimized out>) at /usr/src/sys/kern/kern_descrip.c:2338 > #11 0xffffffff804f4ab9 in fdescfree (td=0xfffff80014b094a0) at > /usr/src/sys/kern/kern_descrip.c:2106 > #12 0xffffffff805013a9 in exit1 (td=0xfffff80014b094a0, rv= optimized out>) at /usr/src/sys/kern/kern_exit.c:369 > #13 0xffffffff80500e3e in sys_sys_exit (td=0xfffffe000782e060, > uap=) at /usr/src/sys/kern/kern_exit.c:179 > #14 0xffffffff80775efd in amd64_syscall (td=0xfffff80014b094a0, > traced=0) at subr_syscall.c:134 > #15 0xffffffff8075b3db in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:396 > #16 0x000000080120335a in ?? () > > Most of the dumps list 'pickup' as current process. All of them have > 'kqueue_close' in the backtrace. > I'm not sure what the next step in diagnosing the issue is. Any pointers > would be greatly appreciated. What is exact revision of the checkout you run, where the panic above occurs ? Please load the kernel.debug + vmcore into kgdb, go to frame 8, and do p *kq p *kn p i p kq->kq_knlist[i].slh_first p *(kq->kq_knlist[i].slh_first)