| Summary: | endless loop in dri_utils.c | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Filippo Carone <f.carone> |
| Component: | Drivers/DRI/r200 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | ||
| Version: | git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Mass version move, cvs -> git DRI-1 code is long dead. |
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.
When I run glxgears (or any other 3D-accelerated software) I see the cpu going at 100% and nothing happening on the screen. I've run glxgears with gdb and I saw the application in stuck on a spinlock in DoBindContext (line 338): (gdb) r Starting program: /usr/bin/glxinfo [Thread debugging using libthread_db enabled] [New Thread 46912524512928 (LWP 11057)] name of display: :0.0 Program received signal SIGINT, Interrupt. [Switching to Thread 46912524512928 (LWP 11057)] 0x00002aaaac5f3629 in DoBindContext (dpy=0x505010, draw=60817410, read=60817410, ctx=0x50ff60, modes=0x50cf10, psp=0x50e1e0) at ../common/dri_util.c:338 338 DRM_SPINLOCK(&psp->pSAREA->drawable_lock, psp->drawLockID); (gdb) any hints?