Date: Mon, 23 Sep 2019 17:32:22 -0400 From: Thomas Laus <lausts@acm.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: freebsd-current@freebsd.org Subject: Re: Booting anything after r352057 kills console Message-ID: <20190923213222.GA57158@mail.laus.org> In-Reply-To: <18332.1569268545@critter.freebsd.dk> References: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190923213222.GA57158>