Date: Sun, 19 Aug 2018 12:47:28 -0500 From: Kyle Evans <kevans@freebsd.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: LUA loader: non UEFI boxes have weird ssh output Message-ID: <CACNAnaE6CH5DL_KtNEY579jMPkh6mUQu4i3gjFNm9_kAL-rDPg@mail.gmail.com> In-Reply-To: <20180819193333.3e7b5785@thor.intern.walstatt.dynvpn.de> References: <20180819193333.3e7b5785@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 19, 2018 at 12:33 PM, O. Hartmann <ohartmann@walstatt.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Just updated some boxes to 12-CURRENT r338057 and I face a very strange behaviour: > > on non-UEFI booting boxes (older Fujitsu and Dell servers from 2008/2009, PCengine APU > 2C4), logging in via ssh reveals broken output: even top does show nothing, the box is > stuck. Calling vi(1) on some files does alos freeze the terminal - no response, nothing. > On the PCengine, also applications like Asterisk do not work anymore - not output on the > console. The program is running, but stopped servicing. Only the serial console to some > of the "ssd-brain-dead" systems work, sshd is dead. This isn't the case on UEFI boxes > with the very same revision (r338057). > > Is this a coincidence or is this/could this related to the switch to LUA loader? > This is probably a coincidence. Most of the important stuff that happens in loader is independent of the interpreter that's built into it, the exceptions being that the interpreter is tasked with reading loader.conf(5) and sets up some ACPI stuff on x86 BIOS boots.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaE6CH5DL_KtNEY579jMPkh6mUQu4i3gjFNm9_kAL-rDPg>