Skip to content

Waag and SOS both stall when legacy UART passthrough #8773

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
YuanXin-Intel opened this issue Apr 27, 2025 · 0 comments
Open

Waag and SOS both stall when legacy UART passthrough #8773

YuanXin-Intel opened this issue Apr 27, 2025 · 0 comments
Labels
status: new The issue status: new for creation

Comments

@YuanXin-Intel
Copy link
Contributor

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:

  1. 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
  2. Launch Windows Guest VM
  3. Open UART in Windows and communicate with peer device
  4. 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:
Image

The log of Windows configuring VT-d entry for UART irq:
Image

@YuanXin-Intel YuanXin-Intel added the status: new The issue status: new for creation label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: new The issue status: new for creation
Projects
None yet
Development

No branches or pull requests

1 participant