Okay... maybe not. This error message appears to not be in -intel,
libdrm, mesa, or xserver. Probably in the kernel. So not something we
can easily suppress.
@Gonzhauser, I do not see instances of your OpenGL fences message in
mesa. Maybe you should report those warnings to the specific
applic
The messages in dmesg aren't important, I agree.
But please note that every OpenGL application
started from a commandline also displays:
get fences failed: -1
param: 6, val: 0
I would consider this a bug. :)
To be fair, the driver made good progress since Intrepid, for example fonts in
Google E
Thanks; maybe for eliminating potential user confusion I can comment it
out for Jaunty.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: High => Low
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Invalid => In Progress
** Changed in: xserver-xorg-video-intel (Ubun
Marking "invalid" because this isn't really a bug, just a informational
message (though yes we could probably make it a little less scary :).
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Invalid
--
*ERROR* Unknown parameter 6
https://bugs.launchpad.net/bugs/353049
Y
Parameter 6 is probably I915_PARAM_NUM_FENCES_AVAIL, which is only part
of 2.6.29+ kernels. The error is harmless though; the driver should
fall back gracefully. Likewise, parameter 4 is
I915_SETPARAM_NUM_USED_FENCES, the other half of the new fence
management code.
The driver used to check drm
** Summary changed:
- kernel drm, libdrm, xserver-xorg-video-intel out of sync
+ *ERROR* Unknown parameter 6
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Triaged
--
*ERROR* Unknown param
