Skip to content
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

Sometimes the driver seems to die with device error -17 and only recovers via a reboot #218

Open
jian2x opened this issue Jan 18, 2023 · 5 comments

Comments

@jian2x
Copy link

jian2x commented Jan 18, 2023

This is Windows 11 Pro, 3802 driver, 2022.2.5 oneVPL release.

For example, I'm transcoding with FFmpeg decoding with hevc_qsv and transcoding to av1_qsv and it's working fine. I then leave the PC idle for an hour or two, come back and run the exact same command and this time I get the dreaded device error -17 from the tool when trying to decode. It never recovers, repeated attempts with the previously-working command just produce the same errors.

It happens perhaps once or twice a day, apparently randomly. I.e. it is not preceded by any other errors or unexpected behaviour.

I have tried disabliing/renabling the device in control panel, but it seems the only cure is to reboot the PC.

Firstly, is this a known issue?

Secondly, is there another approach I can take from an API level that would "reset" the state of the device?

The GPU is being used only for decoding/encoding. I use the integrated intel GPU for the display.

@jian2x
Copy link
Author

jian2x commented Jan 18, 2023

Issue tracking link : intel/vpl-gpu-rt#290

@deepglugs
Copy link

is this what you see?

[av1_qsv @ 0x561a7e2dac80] Error during set display handle
: device failed (-17)

@ma3uk
Copy link

ma3uk commented Feb 16, 2023

I have a similar problem. The problem may arise without leaving the PC, but simply by starting a new encoding process immediately after the previous one, the error may be either -17 or -16

@wenbinc-Bin
Copy link
Contributor

Hi @deepglugs According to your comment in #233, your problem seems to be solved.

Hi @ma3uk Could you please also try this way to fix your environment? Make sure libmfx-gen1.2.so is installed in you environment. You can install it by command apt install libmfx-gen1.2. Than run command:
./ffmpeg -loglevel verbose -hwaccel qsv -i ./input.mp4 -c:v av1_qsv -y output.mp4
Try to find this information in log:
[AVHWDeviceContext @ 0x5557af915940] Initialize MFX session: implementation version is 2.8
2.x means vpl runtime, 1.x means MSDK runtime.

@xhaihao
Copy link
Contributor

xhaihao commented Mar 2, 2023

@jian2x Do you still have this issue ? If yes, could you try with FFmpeg 6.0 and the latest driver from https://www.intel.com/content/www/us/en/download/726609/intel-arc-iris-xe-graphics-whql-windows.html ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants