[Bug] UART has txfifo bug #3046
Labels
Priority: Low
Indicates that an issue or pull request should be resolved behind issues or pull requests labelled `
Status: Parked
Indicates that an issues or pull request will be revisited later
Type: Bug
Indicates an unexpected problem or unintended behavior
Comments
cperciva
added
the
Type: Bug
mattschlebusch
added
the
Priority: Medium
|
It may need this PR in rust-vmm first: rust-vmm/vm-superio#96 |
pb8o
added
Priority: Low
ShadowCurse
added
the
Status: Parked
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Just tripped over this with FreeBSD: I need to set hw.broken_txfifo=1 to make the UART work once we enter userland in a Firecracker VM. This is a workaround I added to FreeBSD about a decade ago to address a QEMU/Xen bug which has long since been fixed there -- IIRC after the txfifo filled up, we wouldn't get an interrupt telling us when it had drained.
I haven't looked into the Firecracker UART code to see what's going on there; I'm opening this mainly as a placeholder so I don't forget to take a look at it later.
To Reproduce
Boot FreeBSD in Firecracker.
Expected behaviour
The UART should work. Instead, once FreeBSD hits userland it writes 16 characters and then gets stuck.
Environment
Running aljimenezb's pvh-v2 branch. FreeBSD HEAD with Firecracker hacks. m5.metal EC2 instance.
The text was updated successfully, but these errors were encountered: