From owner-freebsd-current@freebsd.org Thu Mar 30 13:26:13 2017 Return-Path: Delivered-To: freebsd-current@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 5C561D24B4A for ; Thu, 30 Mar 2017 13:26:13 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 390AC79D for ; Thu, 30 Mar 2017 13:26:13 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mailman.ysv.freebsd.org (Postfix) id 385E8D24B49; Thu, 30 Mar 2017 13:26:13 +0000 (UTC) Delivered-To: current@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 3805BD24B48 for ; Thu, 30 Mar 2017 13:26:13 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f68.google.com (mail-lf0-f68.google.com [209.85.215.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9B8479C for ; Thu, 30 Mar 2017 13:26:12 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f68.google.com with SMTP id v2so4600580lfi.2 for ; Thu, 30 Mar 2017 06:26:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BeIHLSdhIj8/8mjTatQzrXOEmKNyqMpTuD1IoHBXiIk=; b=kxs3Dqd85pCxR4RQR9D0MVb3Fy52Jfj7p4NQ7TpEtPTrS9aR9Tx6tUwBoHXTiP27wm qkvI+BXEuzV091G/+N64RC6oMC3oAGFEf1dS+gDpMu0L1GwmXs2ves2mtCUPZ6giRlK8 T5wMVsaa4WRnFdRbYfCG6+JOTZYj0ufFu9bSVio3BpbCk6IeOwb+2RVNaeUV9G4nC8e5 o5DNXsfnVmE7wl3i4H8d8RdnXXKeHigwyhXGnEVyuAIVAHYJyttQi0KxKMa/u8lTqhe2 N0gdv8r2O13mRYDmLpKkz1Q8LsPppA4VJ6ItcDbH4s4HJD1RQy2dYGobPGQuEkInMWwh cd+A== X-Gm-Message-State: AFeK/H1IKObjbgQib20VmbOL+jjd1NlCINLecm6CWZHvpMNhkoPtbJhmu/9lcfgwCszibg== X-Received: by 10.25.202.29 with SMTP id a29mr1829162lfg.23.1490880370295; Thu, 30 Mar 2017 06:26:10 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id f28sm375312lfi.52.2017.03.30.06.26.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 06:26:09 -0700 (PDT) Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others To: Andriy Gapon , Bruce Evans References: <7d5bbbf0-6908-185c-2ee0-29e0a4f60591@freebsd.org> <5587c798-d36c-9074-1060-30e206db5571@freebsd.org> <69af07a7-ec8f-9b7f-8b93-9ba148f30fec@freebsd.org> <8C24D1BA-1607-4C19-BA38-39256E82C7AF@gmail.com> <51045bee-a626-efb3-4b1e-0c3d36abb1ab@freebsd.org> <20170329132927.U882@besplex.bde.org> <20170330150449.R1061@besplex.bde.org> <3534bbeb-9f73-4e37-8f89-c05dd9f89f8c@freebsd.org> <20170330183716.W1655@besplex.bde.org> <4085b441-74ee-796f-adc0-713dfc198b03@freebsd.org> <1772f54a-4268-577a-8e7f-abce929d39c8@freebsd.org> Cc: "Ngie Cooper (yaneurabeya)" , bde@FreeBSD.org, current@FreeBSD.org From: Andrey Chernov Message-ID: <365b1846-ee24-00f5-9498-63b3a290483a@freebsd.org> Date: Thu, 30 Mar 2017 16:26:08 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 13:26:13 -0000 On 30.03.2017 14:23, Andriy Gapon wrote: > On 30/03/2017 12:34, Andrey Chernov wrote: >> On 30.03.2017 12:23, Andrey Chernov wrote: >>> Yes, only for reboot/shutdown. The system does not do anythings wrong >>> even under high load. On reboot or hang those lines are never printed: >>> >>> kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done >>> kernel: Waiting (max 60 seconds) for system process `bufdaemon' to >>> stop...done >>> kernel: Waiting (max 60 seconds) for system process `syncer' to stop... >>> kernel: Syncing disks, vnodes remaining...5 3 0 1 0 0 done >>> kernel: All buffers synced. >>> (it is from 10-stable sample, old -current samples are lost) >>> >>> Moreover, GELI swap deactivation lines are never printed too (I already >>> mention that I change swap to normal, but nothing is changed). >> >> I start to have raw guess that _any_ kernel printf in shutdown mode >> cause not printf but premature reboot. > > This sounds somewhat familiar... > I vaguely recall an opposite issue that happened in the past. After one of my > changes the reboot started hanging for one user. Turned out that the actual bug > was always there, but previously the system rebooted because of a printf that > caused a LOR (between spinlocks, AFAIR), witness tried to report it... using > printf, and that recursed and there was a triple fault in the end. > > Let me try to dig some details, maybe the current issue is related in some ways. > > By chance, do you have WITNESS but not WITNESS_SKIPSPIN in your kernel config? No, I don't have WITNESS* I think removing all vt* lines from the kernel confing (and leaving sc) will be enough to reproduce it, but I am not sure.