From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016 Description of problem: Version-Release number of selected component (if applicable): kernel-2.6.3-2.1.253.2.1 How reproducible: Always Steps to Reproduce: 1. enable dri uasge in XF86Config 2. init 5 3. glxgears Actual Results: x server frozen Expected Results: accelerated gfx output Additional info:
1) what hardware is this ? 2) can you copy relevant parts of the oops ?
Created attachment 98928 [details] oops #1
Created attachment 98929 [details] oops #2
Created attachment 98930 [details] oops #3
Created attachment 98931 [details] oops #4
Created attachment 98932 [details] oops #5
Created attachment 98933 [details] cat /proc/cpuinfo
Created attachment 98934 [details] lspci -vv
Created attachment 98935 [details] cat /proc/mtrr
Created attachment 98936 [details] dmesg
Created attachment 98937 [details] dmidecode
its a centrino based notebook (alienware area51-m;sentia) remarks: 1. the intel windows gfx driver reports 64MB memory for the gfx adapter while agpgart reports 128M; this is (in principle) a dual head system, so agpgart doesn't get it? 2. i've seen one report on lkml that the i830 should be extended for i855 (as it has been for i845) 3. i currently have the agp/drm stuff in-kernel but i will build another kernel where they are modularized (again); if nesssecary i can (again) provide the oops traces 4. i can successfully shutdown (through acpid tracking pwrbtn usage); so the system is still stable only the x server hangs
triage->duplicate 117713 duplicate of bug 117713
ah this one I fixed last week ;) see the kernel on http://people.redhat.com/arjanv/2.6/
*** This bug has been marked as a duplicate of 117713 ***
still not working 2.6.4-1.298, dmesg: Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected an Intel 855 Chipset. agpgart: Maximum main memory to use for agp memory: 933M agpgart: Detected 8060K stolen memory. agpgart: AGP aperture is 128M @ 0xf0000000 mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 [drm] Initialized i830 1.3.2 20021108 on minor 0 mtrr: base(0xf0020000) is not aligned on a size(0x800000) boundary mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 [drm:i830_wait_ring] *ERROR* space: 128384 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 [drm:i830_wait_ring] *ERROR* space: 131056 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup mtrr: base(0xf0020000) is not aligned on a size(0x800000) boundary mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 [drm:i830_wait_ring] *ERROR* space: 130648 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup mtrr: base(0xf0020000) is not aligned on a size(0x800000) boundary mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 [drm:i830_wait_ring] *ERROR* space: 130648 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup mtrr: base(0xf0020000) is not aligned on a size(0x800000) boundary mtrr: 0xf0000000,0x8000000 overlaps existing 0xf0000000,0x400000 i checked with the kernel rpm as well as a modularized self-built one btw. since this bug is now a duplicate where should i add future comments?
When bugs are closed as a duplicate of another bug, future comments should be added to the master bug, so the issue can be tracked in one location. Hope this helps.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.