From owner-freebsd-stable@freebsd.org Fri Jun 22 10:44:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B752F1016BEE for ; Fri, 22 Jun 2018 10:44:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F78C8AD0A for ; Fri, 22 Jun 2018 10:44:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4279322355; Fri, 22 Jun 2018 06:44:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 22 Jun 2018 06:44:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=eYpimuUX4nFFiR8uRAFnIYaMaHE6g n9L41vQP4aRSs0=; b=bL8jamf+e/LDoyi529/W4HPB5wPfpWkAvAD3AQnV6aHue bY4eekC9Pru/fHlZ6hyWHVG5H3bvBGCOjMNCgp/QqpB6gAz9IwhBqFScTu4NJhK7 Y2TDax7otjREoMKT4DgjEH3nS7V9YpNwM24lHR2BruvIAGD7Pj7rjcWnOMnQDEZJ wEhPAz57HH+t+xAlzHjEWMtIY1EE4vc9m41FihhH37O5N+GuqRtOrJt/Jd32yE+6 FGyZTNjLbE1V5TemzM3uWSrI/q/bMi9RJKjWOhjVkTuj4HZObyD33GHOWKQql/aJ jjtSJwn1o1+e0cktz9PHl4XBVo2CGBKdvnhQUEJhw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=eYpimu UX4nFFiR8uRAFnIYaMaHE6gn9L41vQP4aRSs0=; b=BoyrgOt/ayLBB8dsS6QQzq lGp5+CDAJfzX1FU+b/vS0TkzNWdfhhm0n/9/AcmNezxpalx8SP2M6SIIrDg402Hd +kyCwzvuM1DFgxg4e00m7WUKKIWkMlSz8OqIxa9Lkak71lHS55dzQ778p4+WsgTp SYdaAKPHZ6hFdiEh+AZWK5+TDB0STQmu5PbnB/ThLniQ7uaQATXsAikBYOCNr+8e YPN9KBvdSZfiuc3WRMOl/9C61Uz4Dao+dhvGmtBW0+cyK7X3n/u7fENnP79igA0x mvDrTDrFPs3zYL/N3a+VsqdvmYlzQdqme/DNQfNKJ1WQ1wE/lRFJqK43dlgewdIQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 8414F10387; Fri, 22 Jun 2018 06:44:30 -0400 (EDT) From: tech-lists Subject: Re: Console is broken after updating to 11.2-RELEASE To: Yasuhiro KIMURA , freebsd-stable@FreeBSD.org References: <20180622.170720.1809136341323718366.yasu@utahime.org> Organization: none Message-ID: Date: Fri, 22 Jun 2018 11:44:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 10:44:38 -0000 Hi, On 22/06/2018 09:07, Yasuhiro KIMURA wrote: > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. I've seen this effect elsewhere. Not exactly the same, but it's been happening with me on some systems since 11.1. The context I see it is when spinning up a bhyve instance in screen. I see a bit more than just booting, something like "unreferenced ps/2 interrupt" after "Booting...". The bhyve instance itself is fully functional. Logging into the bhyve instance through ssh I can see its dmesg and it all looks OK. However, if in syslogd.conf I enable console logging via console.log and reboot, *nothing gets written to it*. Have had this issue for about a year now, not been able to fix it. Frustratingly, it doesn't happen with all VMs. I've not seen it happen with a 12-current VM, just 11-stable. And even then, not *all* 11-stable VMs. -- J.