Summary: | SIGSEGV when using 0 for YUV values | ||
---|---|---|---|
Product: | Mesa | Reporter: | pauldotknopf |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED NOTABUG | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 17.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | apitrace of error |
Description
pauldotknopf
2017-11-28 02:33:54 UTC
Here is vainfo output, if it is relevant. libva info: VA-API version 0.39.4 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.39 (libva 1.7.3) vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice Also, here is my xrandr output. eDP1 connected primary 800x480+0+0 (0x49) normal (normal left inverted right x axis y axis) 430mm x 290mm Identifier: 0x42 Timestamp: 11376 Subpixel: unknown Gamma: 1.3:1.3:1.3 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff000d12117570030000 05180104a52b1d78e28042ac5130b425 10505300000001010101010101010101 010101010101b80b208030e02d102830 d300d39e0000001e0000000000000000 00000000000000000000000000fd0038 4c1e5311000a202020202020000000fc 00636837353131620a20202020200022 BACKLIGHT: 0 range: (0, 100) Backlight: 0 range: (0, 100) scaling mode: Full aspect supported: None, Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 800x480 (0x49) 30.000MHz +HSync +VSync *current +preferred h: width 800 start 840 end 888 total 928 skew 0 clock 32.33KHz v: height 480 start 493 end 496 total 525 clock 61.58Hz 640x480 (0x105) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz 400x240 (0x106) 6.944MHz -HSync +VSync h: width 400 start 392 end 424 total 448 skew 0 clock 15.50KHz v: height 240 start 241 end 244 total 250 clock 62.00Hz DP1 disconnected (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 11376 Subpixel: unknown Clones: HDMI1 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on DP2 disconnected (normal left inverted right x axis y axis) Identifier: 0x44 Timestamp: 11376 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on DP3 disconnected (normal left inverted right x axis y axis) Identifier: 0x45 Timestamp: 11376 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on HDMI1 disconnected (normal left inverted right x axis y axis) Identifier: 0x46 Timestamp: 11376 Subpixel: unknown Clones: DP1 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on VIRTUAL1 disconnected (normal left inverted right x axis y axis) Identifier: 0x47 Timestamp: 11376 Subpixel: no subpixels Clones: CRTCs: 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: Could you supply a test program or apitrace of it? https://github.com/apitrace/apitrace Created attachment 135772 [details]
apitrace of error
(In reply to pauldotknopf from comment #3) > Created attachment 135772 [details] > apitrace of error Thanks, I'm getting "warning: could not guess trace's API" though. Unfortunately we probably have uncompatible versions of apitrace :/ (In reply to pauldotknopf from comment #3) > Created attachment 135772 [details] > apitrace of error Can you please check the version of your apitrace ? Also can you please reload apitrace output, probably it was broken ? There was a race condition in my software. The buffer being sent was being changed, in transit. Adding proper locks resolved the issue. I'm guessing the mesa drivers work better/more efficiently with 0 values, causing this race condition to happen. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.