Red Hat Bugzilla – Bug 186016
Xorg i810 server freeze: "INVALID MEM ALLOCATION"
Last modified: 2012-05-04 01:47:46 EDT
Description of problem:
XOrg server using i810 freezes and won't release console.
Version-Release number of selected component (if applicable):
How reproducible: every time
Steps to Reproduce:
1. start X on FC5 on laptop using i810 driver.
2. screen freezes or blanks.
CTRL-ALT-BACKSPACE, other keys, "kill", "kill -9" do not release console.
Server log reports "INVALID MEM ALLOCATION". Many user logs were submitted at
X should start
This problem has been identified and a workaround found on
I patched the FC5 rpms to include the workaround at
http://sw.sbay.org/fc5/i810-video-workaround-20060320/ (patch file with
one-liner change attached)
As noted by a commenter on the freedesktop.org bugzilla, this is a workaround,
not a fix. It comments out a call to ValidatePCI() in the core server, which is
"invasive" (as the commenter over there says.) However, this worked for me,
making the difference between "doesn't work at all" and "seems to work fine so
far." So I consider it important information in helping you diagnose the real
Created attachment 126370 [details]
patch to implement temporary workaround from freedesktop.org
I am also suffering same problem. Because anaconda had been freeze I could even
install FC5 from FC5 CD. I installed FC4 and updated to FC5 using yum. Now I
used vesa driver.
The upstream bug above has been marked as a duplicate of
https://bugs.freedesktop.org/show_bug.cgi?id=6750 which has been closed
now as fixed in X11R7.1
There is also indication that this is actually a hardware bug, and that the
"fix" is a workaround for that hardware bug.
Closing bug as "RAWHIDE" as we have 7.1 in rawhide currently, however we
are also planning on releasing it as an FC5 update in the future.