You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When passthrough legacy UART (on super IO chip) to Waag. Windows UART driver could initialize the UART. But once send or receive data through UART, Waag would stall and SOS would stall too.
Codebase
ACRN release 3.3
Scenario
SOS + Windows as post launch VM
To Reproduce
Steps to reproduce the behavior:
Passthrough legacy UART to Waag with "acpidev_pt" option in launch script, for example: --acpidev_pt PNP0501,uid=12,type=io_port,min=0x248,len=8 --acpidev_pt PNP0501,uid=12,type=irq,irq=11
Launch Windows Guest VM
Open UART in Windows and communicate with peer device
Waag and even SOS stall
Expected behavior
UART passthrough to Windows could communicate with peer device
Additional context
Attach the following logs if available:
The log of windows configuring the vioapic for UART irq:
The log of Windows configuring VT-d entry for UART irq:
The text was updated successfully, but these errors were encountered:
Describe the bug
When passthrough legacy UART (on super IO chip) to Waag. Windows UART driver could initialize the UART. But once send or receive data through UART, Waag would stall and SOS would stall too.
Codebase
ACRN release 3.3
Scenario
SOS + Windows as post launch VM
To Reproduce
Steps to reproduce the behavior:
--acpidev_pt PNP0501,uid=12,type=io_port,min=0x248,len=8 --acpidev_pt PNP0501,uid=12,type=irq,irq=11
Expected behavior
UART passthrough to Windows could communicate with peer device
Additional context

Attach the following logs if available:
The log of windows configuring the vioapic for UART irq:
The log of Windows configuring VT-d entry for UART irq:

The text was updated successfully, but these errors were encountered: