From owner-freebsd-current@freebsd.org Thu Mar 30 09:23:53 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 A663CD2278D for ; Thu, 30 Mar 2017 09:23:53 +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 84C49AAB for ; Thu, 30 Mar 2017 09:23:53 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mailman.ysv.freebsd.org (Postfix) id 8068CD2278B; Thu, 30 Mar 2017 09:23:53 +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 800C7D22789 for ; Thu, 30 Mar 2017 09:23:53 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) (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 0E251AA5 for ; Thu, 30 Mar 2017 09:23:52 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f66.google.com with SMTP id v2so4002061lfi.2 for ; Thu, 30 Mar 2017 02:23:52 -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=sSkBCcfxTVd8vBo0jsiOEVv8iC90Z4UCFlrVVjv8Jjo=; b=dRpe5cb7g9PooCpl/wICLeAMbtbxOlisAlOYNglfEBZOjDcLge9LxgA7nSoA8+pmYM lHNntyCkennqKjqiJ5h4uwoii61WSNhSgjjKK0pQ+QlPb/izNVc5wsgGn9ycKpc8UtIW F3UU5JbNwaLsJ1q2dArSMPygzAjhDkLKnz5Bc1fCuJdGmGXRK/ibNK8I8oj09FnmJAVu nZxnJxaMz4rEsimSBHNcPcR4EJcsBmDOQDfDzvM6G5+l3bglBP0BE+WKe33HFS72wFwa ZFzCsxJO4PkShRuHgHDdb3WuEnxIpWVi+jjlEEQ/Ov2cYVug2HMxKYpBv0jr2Isfkyix adVQ== X-Gm-Message-State: AFeK/H2DYci20PQjEmEH23Jr7Q7GcT2nDNMtJcyD/0M4cbSBdv5ksOalVR/vlA+u2A+y5w== X-Received: by 10.25.18.95 with SMTP id h92mr1281906lfi.63.1490865830930; Thu, 30 Mar 2017 02:23:50 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id o100sm276183lfi.18.2017.03.30.02.23.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 02:23:50 -0700 (PDT) Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others To: 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> Cc: "Ngie Cooper (yaneurabeya)" , bde@freebsd.org, current@freebsd.org From: Andrey Chernov Message-ID: <4085b441-74ee-796f-adc0-713dfc198b03@freebsd.org> Date: Thu, 30 Mar 2017 12:23:49 +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: <20170330183716.W1655@besplex.bde.org> 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 09:23:53 -0000 > We don't understand the bug yet. It might not even be in sc. Do you only > see problems for shutdown? The shutdown environment is special for > locking. 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). > A hang in sc means that deadlock occurred and sc's new deadlock detection > didn't work. Hangs are rare. Most common are premature reboots. > Check that ddb works before shutdown, or just put a lot of printfs in I can't check it ddb because I can't enter ddb in sc mode, as I already write, nothing happens. Only vt mode allows Ctrl-Alt-ESC, but the bug does not exist in vt mode, so it is pointless. >>> You might have entered ddb in a context which used to race or deadlock. >> >> No. I try about 20 times on machine which does nothing and can't enter >> KDB in sc only mode, but got one dead hang instead, when start to repeat >> it too fast. > > Even earlier than shutdown, and when booting? I mean in normal operation mode after booting, earlier than shutdown. Shutdown with premature reboot is too fast to press anything at the right time. I don't try to enter ddb when booting yet, but tell you results later. > I call this line-drawing characters for cp437, and use them occasionally, > but I don't know the termcap method for using them very well. See ac, as, ae.