From owner-freebsd-current@freebsd.org Mon Sep 23 21:32:30 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 38886121877 for ; Mon, 23 Sep 2019 21:32:30 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ccws0vFCz4Z60 for ; Mon, 23 Sep 2019 21:32:28 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id CVwViAJqT5SukCVwXiD76U; Mon, 23 Sep 2019 21:32:27 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id x8NLWMUa057259 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 23 Sep 2019 17:32:22 -0400 (EDT) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id x8NLWME3057258; Mon, 23 Sep 2019 17:32:22 -0400 (EDT) (envelope-from lausts) Date: Mon, 23 Sep 2019 17:32:22 -0400 From: Thomas Laus To: Poul-Henning Kamp Cc: freebsd-current@freebsd.org Subject: Re: Booting anything after r352057 kills console Message-ID: <20190923213222.GA57158@mail.laus.org> Reply-To: lausts@acm.org References: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18332.1569268545@critter.freebsd.dk> X-Operating-System: FreeBSD 12.0-RELEASE-p10 on an amd64 User-Agent: Mutt/1.12.1 (2019-06-15) X-CMAE-Envelope: MS4wfCLz5rP8DQzkG/CZ2nO0xlprrySWryxH3j+UrjPN7nlYpFZiUPs7kwRRmcY+n79BCY3+5izA/QGjlCovP5YHGrAT5ETQUYnnNPiklJGLB3vi7rgbHFtC DJFV18uNTZ6YMa3Ay3i3Wmu+r/BwOeM1nYq9qnsRUDYndtVbiX9cdQnYiU9HpH0ALgjhRx3E1nykghn8bHhGmxRJ8EL+aQ8IhTk= X-Rspamd-Queue-Id: 46ccws0vFCz4Z60 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of lausts@laus.org has no SPF policy when checking 107.14.166.227) smtp.mailfrom=lausts@laus.org X-Spamd-Result: default: False [-1.67 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[lausts@acm.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.992,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.992,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[acm.org]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[227.166.14.107.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[lausts@acm.org,lausts@laus.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[227.166.14.107.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14065, ipnet:107.14.160.0/20, country:US]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,lausts@laus.org]; IP_SCORE(-0.89)[ipnet: 107.14.160.0/20(-2.43), asn: 14065(-1.95), country: US(-0.05)]; RECEIVED_SPAMHAUS_PBL(0.00)[189.112.29.65.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 23 Sep 2019 21:32:30 -0000 Poul-Henning Kamp [phk@phk.freebsd.dk] wrote: > -------- > In message <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org>, Thomas Laus writes: > > >Where do I go from here? The computer is an Intel i5 Skylake with > >onboard graphics. > > Based on personal experience: > > 1. Deinstall drm ports > > 2. Remove all remaining drm related files under /boot > > 3. Reinstall drm port > That did not work. On a successful boot after using beadm to rollback to r352057, I see the following items startup after setting the ntpd security policy: starting ntpd configuring vt: blanktime sanity check of sshd configuration start sshd start sendmail & sendmail submit as well as cron start background checks login On all svn updates after r352057, the last item logged is the ntpd security policy and then the console goes black. The computer is dead and I can't login through ssh nor change to another console. I hae to hit the reset switch to reboot. Even ctrl-alt-delete is not functioning. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF