Skip to content

Commit 716b87c

Browse files
authored
Update FAQ.md
1 parent 48b0551 commit 716b87c

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

vllm/FAQ.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@
1616
- [How can I verify if the benchmark data from `platform_basic_evaluation.sh` is valid?](#how-can-i-verify-if-the-benchmark-data-from-platform_basic_evaluationsh-is-valid)
1717

1818
## Tools
19+
- [Why do I always see `2.5GT/s` PCIe link status in `lspci`](#why-do-i-always-see-2.5gt/s-pcie-link-status-in-lspci)
1920
- [Why can't I see `xpu-smi` in the `vllm` Docker image?](#why-cant-i-see-xpu-smi-in-the-vllm-docker-image)
2021
- [Why can't I see GPU utilization with `xpu-smi`?](#why-cant-i-see-gpu-utilization-with-xpu-smi)
2122

@@ -100,6 +101,9 @@ These data points are collected from internal evaluations using an Intel® Xeon
100101

101102
# Tools
102103

104+
## Why do I always see `2.5GT/s` PCIe link status in `lspci`
105+
It's an known issue but no real impact on GPU operation. Official explaination: https://www.intel.com/content/www/us/en/support/articles/000094587/graphics.html
106+
103107
## Why can't I see `xpu-smi` in the `vllm` Docker image?
104108

105109
Due to release process limitations, `xpu-smi` is currently not included in the official `vllm` Docker image.

0 commit comments

Comments
 (0)