-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Invalid probability vector error with AMD iGPU on Vulkan backend Environment #2596
Comments
MacBook Pro 16 inch 2019 with AMD 5500M has issue with Vulkan-loader 1.3.302 ggml_vulkan: Found 1 Vulkan devices: system_info: n_threads = 4 / 16 | AVX = 1 | AVX2 = 1 | AVX512 = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | SSE3 = 1 | SSSE3 = 1 | VSX = 0 | COREML = 0 | OPENVINO = 0 | main: processing '/Volumes/Share/Streams/audio/voices/c4.wav' (160000 samples, 10.0 sec), 4 threads, 1 processors, 5 beams + best of 5, lang = auto, task = transcribe, timestamps = 1 ... whisper_full_with_state: auto-detected language: af (p = 0.010000) whisper_print_timings: load time = 368.12 ms |
BTW, if I revert to version 1.7.2 release(git: 6266a9f), then result is OK, and output right. And same code in Linux with 1080Ti vulkan backend also is correct。 |
The issue was fixed in my environment by modifying the line |
Environment
OS: Windows 11
CPU: AMD Ryzen 7 7840u
GPU: AMD Radeon 780M (iGPU)
Model: ggml-tiny.bin
whisper.cpp: Both latest version from main branch and 1.7.2
Issue Description
When using Release build with Vulkan backend on AMD GPU, the output becomes garbled (showing timestamps with exclamation marks) and the output changes between runs. To investigate this issue, I switched to Debug build which revealed an underlying problem with probability calculations.
Steps to Reproduce
First with Release build:
Output from Release build:
Then with Debug build to investigate:
Error in Debug Build
This issue appears to be related to whisper.cpp#2400.
I thought it might be connected to llama.cpp#10434, so I tried applying the same fix, but it didn't improve the situation. Any suggestions on how to resolve this would be appreciated.
The text was updated successfully, but these errors were encountered: