On 2022-10-26 at 17:15 EDT, Colin Percival wrote:
On 10/26/22 13:48, Ed Maste wrote:
On Mon, 24 Oct 2022 at 22:11, void wrote:
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 Fi
On Wed, Oct 26, 2022 at 02:15:29PM -0700, Colin Percival wrote:
Indeed, looking at usr.sbin/bhyve/uart_emul.c it looks like FCR_XMT_RST is
not emulated. This is different from Firecracker, which doesn't emulate
either anything from the FCR and where I was seeing the receive side not
being flush
On 2022-10-27 20:57, Matteo Riondato wrote:
> On 2022-10-26 at 17:15 EDT, Colin Percival wrote:
>
>>On 10/26/22 13:48, Ed Maste wrote:
>>>On Mon, 24 Oct 2022 at 22:11, void wrote:
this started appearing in dmesg
ns8250: UART FCR is broken
ns8250: UART FCR is broken
>>>
>>>This m
On 26 Oct 2022, at 22:29, Chen, Alvin W wrote:
> Any body know the status to support P Core and E Core?
> Now WA is: disable PCID.
Disabling vm.pmap.pcid_enabled is the best workaround for now.
There has been some progress in investigations in the background, but I
don’t think there is a permanen