Summary: | 8064px Max OpenGL window resolution i965 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Inad <inadsan> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 18.0 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
glxinfo
cpuinfo xrand xorglog dmesg Image Ubuntu 17.10 |
Description
Inad
2018-04-20 08:16:32 UTC
I cannot reproduce this. Can you please include some information about your system? Please include the output given by glxinfo. Created attachment 139039 [details]
glxinfo
Created attachment 139040 [details]
cpuinfo
Created attachment 139041 [details]
xrand
Created attachment 139042 [details]
xorglog
Created attachment 139043 [details]
dmesg
Created attachment 139044 [details]
Image
With the final table version 18 also happens I'm going to try other distributions Created attachment 139051 [details]
Ubuntu 17.10
In ubuntu glxgears it works fine, but when you connect the third 4K monitor you see the same corruption in the background (trash image)
(In reply to Inad from comment #9) > Created attachment 139051 [details] > Ubuntu 17.10 > > In ubuntu glxgears it works fine, but when you connect the third 4K monitor > you see the same corruption in the background (trash image) You did not mention multimonitor setup before, was this also the case when testing on gentoo? I think your bug might be somewhere else than Mesa, probably X driver (?) Did you try if using modesetting makes difference? modesetting has a maximum resolution of 8xxx. I do not remember it now exactly With the intel driver yes that allows me these resolutions. I think it's the mesa driver because the error only happens with an OpenGL window. With a gtk2 window with a simple button there is no problem, with the basic example of OpenGL triangle causes corruption. With LIBGL_ALWAYS_SOFTWARE = 1 both with LLVMpipe and with swrast it works fine LLVMpipe max 9664 px for limits (In reply to Inad from comment #11) > modesetting has a maximum resolution of 8xxx. I do not remember it now > exactly > > With the intel driver yes that allows me these resolutions. > I think it's the mesa driver because the error only happens with an OpenGL > window. > With a gtk2 window with a simple button there is no problem, with the basic > example of OpenGL triangle causes corruption. > > With LIBGL_ALWAYS_SOFTWARE = 1 both with LLVMpipe and with swrast it works > fine > LLVMpipe max 9664 px for limits Does it work with only single or dual monitor setup? If it does, then the bug is in whatever X does in displaying image within multiple monitors. I can`t reproduce this issue on my laptop with those configuration of displays: Base: 1920x1080 VGA: 1920x1080 Displayport: 3840x2160 Other configuration of my system: Kernel: 4.16.13-041613-generic mesa: Mesa 18.0.0-rc5 GPU: Intel(R) HD Graphics 620 (Kaby Lake GT2) Xserver-xorg Version: 1:7.7+19ubuntu7 OS: Ubuntu 18.04 I ran glxgears with these resolutions: 7681x2160, 7681x1080, 8065x2160. Hello Inad, Please, provide additional information about your system. This bug looks similar to https://bugs.freedesktop.org/show_bug.cgi?id=98297. In that post reporter used "modesetting driver", which does not support target resolution. Please send output of this command "inxi -Gxx". If you use modesetting try to reproduce this issue with xf86-video-intel DDX driver. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1717. |
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.