Bug 203960 - glxgears crashes
Summary: glxgears crashes
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-i810
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-24 18:17 UTC by Jurgen Kramer
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-09 15:49:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jurgen Kramer 2006-08-24 18:17:20 UTC
Description of problem:
when running glxgears to check if hardware rendering works glxgears crashes

Version-Release number of selected component (if applicable):


How reproducible:
xorg-x11-drv-i810-1.6.5-4.fc6
mesa-libGL-6.5.1-0.rc1.fc6
mesa-libGLU-6.5.1-0.rc1.fc6
mesa-libGLU-devel-6.5.1-0.rc1.fc6
mesa-libGL-devel-6.5.1-0.rc1.fc6


Steps to Reproduce:
1. Start glxgears from terminal
2.
3.
  
Actual results:
libGL warning: 3D driver claims to not support visual 0x5b
Mesa: CPU vendor: GenuineIntel
Mesa: CPU name: Genuine Intel(R) CPU           T2500  @ 2.00GHz
Mesa: MMX cpu detected.
Mesa: SSE cpu detected.
Mesa: Not testing OS support for SSE, leaving enabled.
glxgears: intel_ioctl.c:62: intelEmitIrqLocked: Assertion `((*(int
*)intel->driHwLock) & ~0x40000000U) == (0x80000000U|intel->hHWContext)' failed.
Aborted


Expected results:
glxgears shown zillion fps ;-)

Additional info:

Comment 1 Jurgen Kramer 2006-08-29 17:33:12 UTC
Not fixed with 
xorg-x11-drv-i810-1.6.5-5.fc6
mesa-libGL-6.5.1-0.rc1.2.fc6
mesa-libGLU-devel-6.5.1-0.rc1.2.fc6
mesa-libGLU-6.5.1-0.rc1.2.fc6
mesa-libGL-devel-6.5.1-0.rc1.2.fc6


Comment 2 Jurgen Kramer 2006-09-09 15:49:24 UTC
Problem fixed:

[kramer@macbook ~]$ glxgears 
libGL warning: 3D driver claims to not support visual 0x4b
4785 frames in 5.0 seconds = 956.941 FPS
4856 frames in 5.0 seconds = 971.155 FPS




Note You need to log in before you can comment on or make changes to this bug.