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
Copy file name to clipboardExpand all lines: vllm/FAQ.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@
16
16
-[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)
17
17
18
18
## 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)
19
20
-[Why can't I see `xpu-smi` in the `vllm` Docker image?](#why-cant-i-see-xpu-smi-in-the-vllm-docker-image)
20
21
-[Why can't I see GPU utilization with `xpu-smi`?](#why-cant-i-see-gpu-utilization-with-xpu-smi)
21
22
@@ -100,6 +101,9 @@ These data points are collected from internal evaluations using an Intel® Xeon
100
101
101
102
# Tools
102
103
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
+
103
107
## Why can't I see `xpu-smi` in the `vllm` Docker image?
104
108
105
109
Due to release process limitations, `xpu-smi` is currently not included in the official `vllm` Docker image.
0 commit comments