From owner-freebsd-stable@FreeBSD.ORG Sat Sep 28 15:27:28 2013 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 ESMTP id C0CC5C9F for ; Sat, 28 Sep 2013 15:27:28 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B2252191 for ; Sat, 28 Sep 2013 15:27:28 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id wm4so4070174obc.11 for ; Sat, 28 Sep 2013 08:27:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IfplkxtVbjkoW63EV1Oh7qQ1AiZ8vCM7DgCeYdl61/4=; b=NNv39WE/pPmxz2htQ3oUZQ46LOsTFEi/+PPQIQKpE/1Vz0Zny54s37uxewoFTElrmp gkxmUe8rzLabQk+ShscAQeSgBlw/NBi648HQAQOjYxgZs8FEQKzwzBPfLoQa3g0bRjD5 PrvrtCsrvAKUFQzWfNMQ+ZP7/nTJX+PuJ8yP2q4jWB5lgG9WsY13xIGtkzuxCbDLUFGk lbcDYZv2VK9k/lKQtrn5jBsr8UNw+nZEM2TN0eqHrF3xTJKpdAFZuT65/GO8scszqdWh zKlD7oz4tS9qNWgicEuWzfESM3TByAMxSQmJE2h6kGs8v+pBLrSn1xKKsnaqOQVYRB4U tpdw== MIME-Version: 1.0 X-Received: by 10.60.133.71 with SMTP id pa7mr1091209oeb.44.1380382047745; Sat, 28 Sep 2013 08:27:27 -0700 (PDT) Received: by 10.182.22.161 with HTTP; Sat, 28 Sep 2013 08:27:27 -0700 (PDT) In-Reply-To: <20130928023046.GA1428@rwpc15.gfn.riverwillow.net.au> References: <20130927000728.GB19167@rwpc15.gfn.riverwillow.net.au> <20130927081221.GK41229@kib.kiev.ua> <20130928023046.GA1428@rwpc15.gfn.riverwillow.net.au> Date: Sat, 28 Sep 2013 17:27:27 +0200 Message-ID: Subject: Re: 9.2-RC4 amd64 panic: vm_page_unwire From: Oliver Pinter To: John Marshall Content-Type: text/plain; charset=ISO-8859-1 Cc: Konstantin Belousov , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Sep 2013 15:27:28 -0000 On 9/28/13, John Marshall wrote: > On Fri, 27 Sep 2013, 11:12 +0300, Konstantin Belousov wrote: >> On Fri, Sep 27, 2013 at 10:07:28AM +1000, John Marshall wrote: >> > I'm running 9.2-RC4 on a handful of desktop and server machines (both >> > i386 and amd64). I have seen three panics (all vm_page_unwire) on one >> > of those systems only (amd64 server) during the past week. > >> > The first two panics were triggered when shutting down the ntpd daemon >> > (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a >> > later release (p388) has not triggered the panic. The system panicked >> > again overnight, this time while acting as an sftp server receiving >> > large (GB) files from another system. > >> > I have made the core.txt.[0-2] files available in the following >> > directory. The directory is not browsable. >> > >> > http://www.riverwillow.net.au/~john/92rc4/ >> >> This might be fixed by r254087-r254090 on stable/9. > > Thank you. Those patches applied cleanly to releng/9.2 so I rebuilt a > patched 9.2. I double-checked and verified that the following patched > files in my releng/9.2@255904 working copy were identical to the same > files in stable/9@254090, then I removed /usr/obj/* and built a fresh > system. > > M /usr/src/sys/vm/vm_fault.c > M /usr/src/sys/vm/vm_map.c > M /usr/src/sys/vm/vm_map.h > M /usr/src/sys/vm/vm_object.c > M /usr/src/sys/vm/vm_object.h > M /usr/src/sys/vm/vm_page.c > > The system panicked as follows during shutdown after its first boot. > The corresponding core.txt.3 file is available at the same location > previously posted. > > Fri Sep 27 22:32:18 2013 +1000 > ozsrv04# kgdb kernel.debug /var/crash/vmcore.3 > ... > Unread portion of the kernel message buffer: > . > <118>Stopping watchdogd. > <118>Waiting for PIDS: 1297 > panic: vm_page_unwire: page 0xfffffe023743eb50's wire count is zero > cpuid = 1 > KDB: stack backtrace: > #0 0xffffffff80490278 at kdb_backtrace+0x68 > #1 0xffffffff8045630a at panic+0x21a > #2 0xffffffff8068bac2 at vm_page_unwire+0x102 > #3 0xffffffff80678732 at vm_fault_unwire+0xd2 > #4 0xffffffff80680851 at vm_map_delete+0x171 > #5 0xffffffff80680acf at vm_map_remove+0x5f > #6 0xffffffff80683ea9 at vmspace_exit+0xc9 > #7 0xffffffff8041f3ad at exit1+0x72d > #8 0xffffffff804203ae at sys_sys_exit+0xe > #9 0xffffffff806afc6f at amd64_syscall+0x3bf > #10 0xffffffff8069a717 at Xfast_syscall+0xf7 > Uptime: 7m24s > > I have now seen this panic on a second server as well (also amd64 but > different hardware vendor). This second (unpatched) system also > panicked during shutdown as follows. Corresponding file named > core.txt.0.system2 is available at the same location as above. > > Sat Sep 28 06:19:59 2013 +1000 > panic: vm_page_unwire: page 0xfffffe0429aa5d18's wire count is zero > cpuid = 1 > KDB: stack backtrace: > #0 0xffffffff804e7398 at kdb_backtrace+0x68 > #1 0xffffffff804ad43a at panic+0x21a > #2 0xffffffff80717d42 at vm_page_unwire+0x102 > #3 0xffffffff80704882 at vm_fault_unwire+0xd2 > #4 0xffffffff8070c9c1 at vm_map_delete+0x171 > #5 0xffffffff8070cc3f at vm_map_remove+0x5f > #6 0xffffffff80710069 at vmspace_exit+0xc9 > #7 0xffffffff804764dd at exit1+0x72d > #8 0xffffffff804774de at sys_sys_exit+0xe > #9 0xffffffff8073d7cf at amd64_syscall+0x3bf > #10 0xffffffff80728277 at Xfast_syscall+0xf7 > Uptime: 5m31s try this from 9-STABLE: https://github.com/freebsd/freebsd/commit/98362329be8e2cdefda1988e5e9d32efbc94855f > > -- > John Marshall >