kernel 2.6.28 Xorg 1.5.99.3 xf86-video-intel 2.5.99.1 mesa intel-2008-q4 branch X failed to start and print following kernel message [drm:i915_irq_emit] *ERROR* i915_irq_emit called without lock held, held 0 owner 00000000 de8de9c0
After bisect, below commit cause the problem, revert it could fix the issue. It is strange that my kernel config has "CONFIG_HIGHMEM64G=y", and GEM works with this option. commit ac5c4e76180a74c7f922f6fa71ace0cef45fa433 Author: Dave Airlie <airlied@redhat.com> Date: Fri Dec 19 15:38:34 2008 +1000 drm/i915: GEM on PAE has problems - disable it for now. On PAE systems, GEM allocates pages using shmem, and passes these pages to be bound into AGP, however the AGP interfaces + the x86 set_memory interfaces all take unsigned long not dma_addr_t. The initial fix for this was a mess, so we need to do this correctly for 2.6.29.
I found the same problem that Li Peng in Gentoo with the following versions: xorg-server-1.5.3 xf86-video-intel-2.6.1 media-libs/mesa-7.3 gentoo-sources-2.6.28-r1 (linux kernel 2.6.28.1 ) But, with the same versions of the programs and a new kernel: gentoo-sources-2.6.28-r2 (linux kernel 2.6.28.5) X is starting and working correctly.
*** Bug 21265 has been marked as a duplicate of this bug. ***
FYI, I do get the same kind of problem with 2.6.28.9 on a 945G system xorg server 1.6.0 xf86-video-intel 2.7.0 libdrm 2.4.7 mesa 7.3
Peng, does this still exist in the latest kernel?
(In reply to comment #5) > Peng, does this still exist in the latest kernel? > No, it is be fixed with Dave's agp patch in 2.6.31.
(English message follows) Bonjour, Je suis en congé parental jusqu'au 13 jullet 2009. Pour toute urgence concernant le travail, veuillez contacter Louis Marchand (louis.marchand@verint.com). Hi, I will be out of office until July 13th 2009. For any urgent matters regarding work, please contact Louis Marchand (louis.marchand@verint.com). Hugo
closing as the reporter says it's fixed. If other people still have problem with 2.6.31, please file separate bugs.
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.