Bug 89791

Summary: [BSW regression]frequently click on gnome-shell after run glxgear may cause error.
Product: Mesa Reporter: Ding Heng <hengx.ding>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED WORKSFORME QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: christophe.prigent, mengmeng.meng, shuo.wang
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Xorg log
dmesg

Description Ding Heng 2015-03-27 08:25:33 UTC
Created attachment 114660 [details]
Xorg log

==System Environment==
--------------------------
Regression: Yes, bisect later

Non-working platforms: BSW

==kernel==
--------------------------
origin/drm-intel-testing:drm-intel-testing-2015-03-13

X11: X11R7_64_2015Q1

==Bug detailed description==
-----------------------------
root@x-bsw14:~# glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
311 frames in 5.0 seconds = 62.126 FPS
300 frames in 5.0 seconds = 59.997 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.002 FPS
282 frames in 5.0 seconds = 56.397 FPS
301 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.007 FPS
300 frames in 5.0 seconds = 59.990 FPS
301 frames in 5.0 seconds = 60.004 FPS
300 frames in 5.0 seconds = 59.990 FPS
301 frames in 5.0 seconds = 60.011 FPS
300 frames in 5.0 seconds = 59.982 FPS
301 frames in 5.0 seconds = 60.010 FPS
301 frames in 5.0 seconds = 60.010 FPS
Window manager warning: Log level 6: The program 'gnome-shell' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 46639 error_code 16 request_code 131 (XInputExtension) minor_code 53)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
236 frames in 5.0 seconds = 47.193 FPS
301 frames in 5.0 seconds = 59.996 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.000 FPS
302 frames in 5.0 seconds = 60.203 FPS
300 frames in 5.0 seconds = 59.996 FPS
^C[2]+  Trace/breakpoint trap   (core dumped) gnome-shell

Then the gnome shell's taskbar will disapear.


==Reproduce steps==
---------------------------- 
1)Xinit &
2)Gnome-shell &
3)Glxgears
4)click frequently on the screen.
5)Ctrl + c
Comment 1 Ding Heng 2015-03-27 08:26:13 UTC
Created attachment 114661 [details]
dmesg

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.