From owner-freebsd-stable@FreeBSD.ORG Sat Oct 5 02:46:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A12EB571 for ; Sat, 5 Oct 2013 02:46:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D9422427 for ; Sat, 5 Oct 2013 02:46:18 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id f12so4833419wgh.26 for ; Fri, 04 Oct 2013 19:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JAq78X+/QAVaRKDsINzwBEbr4oQgxsPfrgORMj3nHpk=; b=w6y1m2RdB/lgDKN+NZc8XmhthZzIY+UtcIXTJ8TfgWlzyy0X5YTi6xZVy07fn7FO24 VmPs2URMS0jX0YkgZPaGcRNZPRgDdSVzvHZKWAos2GwsOm4tzRRw40jQo8SF5W8LbdjS hjhnHGSOGx039bGnPyqGZcFPxN4ZMNeVlMT+GXjNvGLS5zWrcg9HXTWiEI1I6WT8Y15D b+4ug2ksYCeFjZeDSsKnFojAIm5Mlsl0+nrWDVVsrEZDj10MB2i3WL4pRqLywDOjg1Ye 63C8QT647mDa2L9hZbWpzJVjNOSevmdp1qkzH9Zzk4ZK5g8kkMtQgS8kNTkqYN2qiafZ TZjQ== MIME-Version: 1.0 X-Received: by 10.194.235.138 with SMTP id um10mr15212642wjc.30.1380941176009; Fri, 04 Oct 2013 19:46:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Fri, 4 Oct 2013 19:46:15 -0700 (PDT) In-Reply-To: <20131004132900.GC20752@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> <20130929212104.GB1370@rwpc15.gfn.riverwillow.net.au> <20130930095507.GD2813@rwpc15.gfn.riverwillow.net.au> <20131004132900.GC20752@rwpc15.gfn.riverwillow.net.au> Date: Fri, 4 Oct 2013 19:46:15 -0700 X-Google-Sender-Auth: d9siz_8Ir9tpK8Q1bF2aj6af4BI Message-ID: Subject: Re: 9.2-RC4 amd64 panic: vm_page_unwire From: Adrian Chadd To: John Marshall Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List 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, 05 Oct 2013 02:46:18 -0000 oh, wait a sec. I think some stuff went in that wired some important processes into memory. -adrian On 4 October 2013 06:29, John Marshall wrote: > On Mon, 30 Sep 2013, 19:55 +1000, 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 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. > > As well as applying those patches to releng/9.2, and still seeing the > panic, I have upgraded one of the systems to stable/9 and still see the > panic. > > > Another data point: both systems on which I have seen this panic have > > the ipmi driver compiled in. ipmi makes the BMC's watchdog timer > > available to the system. > > I ruled this out. I recompiled a kernel with no ipmi driver (so that > removes the watchdog timer too) but the system would still panic on > shutdown when stopping ntpd. > > I have also reverted to the STABLE ntpd distribution (4.6.4p5 > 2011-12-24) and still see the panic. > > I took one of the systems back to releng/9.1 (9.1-RELEASE-p7). Its > kernel includes the ipmi driver, I am running watchdogd, I am running > ntpd, I have rebooted several times and have never seen a panic. > > So, I now have one system on 9.1-RELEASE (panic-free); and the second > system on 9-STABLE (panics). Previously I had both systems on > 9.2-RELEASE and panicking. > > Another common factor with all but one of the panics I have seen is that > the process which appears to trigger the panic is a 'realtime' process. > > rwsrv08# top -b 200 | awk '(/^ PID/ || $5~/^r/)' > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 1739 root 1 -52 r0 12056K 8040K nanslp 7 0:02 0.00% > watchdogd > 1911 root 1 -52 r0F 32668K 18468K select 7 0:02 0.00% ntpd > > Here is a recent stable/9 tripping over watchdogd on shutdown: > > FreeBSD 9.2-STABLE #0 r256029: > . > Stopping watchdogd. > Waiting for PIDS: 1729 > panic: vm_page_unwire: page 0xfffffe042bdae2d8's wire count is zero > cpuid = 1 > KDB: stack backtrace: > #0 0xffffffff804e8188 at kdb_backtrace+0x68 > #1 0xffffffff804adcba at panic+0x21a > #2 0xffffffff80718dd2 at vm_page_unwire+0x102 > #3 0xffffffff80705a52 at vm_fault_unwire+0xd2 > #4 0xffffffff8070db41 at vm_map_delete+0x171 > #5 0xffffffff8070ddbf at vm_map_remove+0x5f > #6 0xffffffff80711199 at vmspace_exit+0xc9 > #7 0xffffffff804773dd at exit1+0x72d > #8 0xffffffff804783de at sys_sys_exit+0xe > #9 0xffffffff8073e86f at amd64_syscall+0x3bf > #10 0xffffffff80729307 at Xfast_syscall+0xf7 > > -- > John Marshall >