Date: Tue, 25 Oct 2022 03:11:28 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: ns8250: UART FCR is broken Message-ID: <Y1dF0CvrJZubFizl@openbsd.local>
next in thread | raw e-mail | index | archive | help
hello freebsd-current@, this started appearing in dmesg ns8250: UART FCR is broken ns8250: UART FCR is broken uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ns8250: UART FCR is broken uart0: console (9600,n,8,1) ns8250: UART FCR is broken ns8250: UART FCR is broken uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 ns8250: UART FCR is broken ns8250: UART FCR is broken ns8250: UART FCR is broken uart2: <16550 or compatible> port 0x3e8-0x3ef irq 4 on acpi0 ns8250: UART FCR is broken The system is a bhyve guest running main-n258723-e0c3f66b4d5f on amd64 with a lightly modified generic-nodebug. There's no physical hardware attached to any com port on the host. Do I need to be concerned with this or is it a known issue? is it a real hardware problem? The host runs many bhyve guests. TIA,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y1dF0CvrJZubFizl>