Date: Wed, 26 Oct 2022 16:48:11 -0400 From: Ed Maste <emaste@freebsd.org> To: freebsd-current@freebsd.org, Colin Percival <cperciva@freebsd.org> Subject: Re: ns8250: UART FCR is broken Message-ID: <CAPyFy2CeWi2_ejv6%2BdKQB6Sa0KLpe0Kq8=p4QNS46HDkADCB9Q@mail.gmail.com> In-Reply-To: <Y1dF0CvrJZubFizl@openbsd.local> References: <Y1dF0CvrJZubFizl@openbsd.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Oct 2022 at 22:11, void <void@f-m.fm> wrote: > > hello freebsd-current@, > > this started appearing in dmesg > > ns8250: UART FCR is broken > ns8250: UART FCR is broken This message was added as part of Colin's work to support FreeBSD in the Firecracker VMM https://cgit.freebsd.org/src/commit/?id=c4b68e7e53bb352be3fa16995b99764c03097e66 In this case it indicates that bhyve has the same bug/missing functionality as Firecracker -- it doesn't implement the FCR_XMT_RST or FCR_RCV_RST bits. You can safely ignore the message, and it will disappear once someone adds the required support to bhyve. We should probably also have the kernel emit the message only once. I've CC'd Colin for comment.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CeWi2_ejv6%2BdKQB6Sa0KLpe0Kq8=p4QNS46HDkADCB9Q>