With the latest git version of the 2d ddx, X hangs before displaying the cursor. Switching back to the console doesn't work. bisecting points at commit 87332a7cc16af82aa47e07fbf90da3635b071dbf Author: Keith Packard <keithp@keithp.com> Date: Mon May 11 13:52:00 2009 -0700 Use drm_intel_bo_disable_reuse API to flag scanout and cursor buffers I'm using kernel 2.6.30-rc6-00043-g22ef37e with KMS. Xorg is 1.6.1 from debian libdrm is libdrm-2.4.11 from git Machine is a IBM ThinkPad X40. VGA part of lspci -v: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA controller]) Subsystem: IBM Device 0557 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at e0000000 (32-bit, prefetchable) [size=128M] Memory at d0000000 (32-bit, non-prefetchable) [size=512K] I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [d0] Power Management version 1 Kernel driver in use: i915 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Subsystem: IBM Device 0557 Flags: fast devsel Memory at e8000000 (32-bit, prefetchable) [size=128M] Memory at d0080000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 1
Created attachment 25963 [details] Xorg.log of the hanging driver
Yifei, can you try 855GM with the unstable (master) build?
We cannot reproduce this on our 855GM, tested on: Platform: 945gm Arch: i386 OSD: Fedora release 10 (Cambridge) Kernel: 2.6.30-rc4 with KMS Libdrm: (master)f57d7f4b0b14972f92a83f155ae8033478aa7729 Mesa: (master)bd59dd69ba0f11f96e627c663c67cc15d1083776 Xserver: (master)4addfcd633484b7f53b5df1b92bfca8bfc1dc48d Xf86_video_intel: (master)87332a7cc16af82aa47e07fbf90da3635b071dbf
Daniel, Keith doesn't believe his patch have any effect at startup time. Could you double check if his commit is culprit? Your log seems incomplete. Could you double check too? Please attach dmesg output.
I've just tested the latest git of libdrm, 2d ddx and linux kernel (mainline). My problem is gone now. Are you still interested in the logs or should I just closed the bug (and reopen it in case the latest changes just papered over the real issue)?
Good to know the latest code is working for you. I think this can be closed now.
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.