Summary: | EBUSY on DRI ioctl when running native google earth | ||
---|---|---|---|
Product: | xorg | Reporter: | Ricardo Cerqueira <fdo> |
Component: | Driver/intel | Assignee: | Alan Hourihane <alanh> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | jbarnes, michel |
Version: | 7.0.0 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Ricardo Cerqueira
2006-06-13 07:11:43 UTC
Sorry, I forgot to add the version details; this is on a FC5 install, using it's stock xorg version (7.0.0) I think Brian Paul has fixed this in Mesa CVS. You should try getting the latest code and building. OK... Mesa CVS took care of the libGL warnings, but the ioctl loop is still here... One thing I hadn't noticed before... It looks like the app is doing the same ioctl twice: the first time works, the second time it fails: gettimeofday({1150330306, 387209}, NULL) = 0 sched_yield() = 0 ioctl(8, 0xc0046444, 0xbfdf42c4) = 0 ioctl(8, 0x40046445, 0xb4ffb288) = 0 ioctl(8, 0x40046445, 0xb4ffb288) = 0 gettimeofday({1150330306, 388262}, NULL) = 0 ioctl(8, 0xc0086446, 0xbfdf428c) = 0 ioctl(8, 0xc010643a, 0xbfdf427c) = 0 ioctl(8, 0xc010643a, 0xbfdf427c) = -1 EBUSY (Device or resource busy) ioctl(8, 0x4008642a, 0xbfdf4254) = 0 ioctl(8, 0xc0046444, 0xbfdf41f4) = 0 gettimeofday({1150330309, 394087}, NULL) = 0 sched_yield() = 0 ioctl(8, 0xc0046444, 0xbfdf42c4) = 0 ioctl(8, 0x40046445, 0xb4ffb288) = 0 ioctl(8, 0x40046445, 0xb4ffb288) = 0 gettimeofday({1150330309, 394523}, NULL) = 0 ioctl(8, 0xc0086446, 0xbfdf428c) = 0 ioctl(8, 0xc010643a, 0xbfdf427c) = 0 ioctl(8, 0xc010643a, 0xbfdf427c) = -1 EBUSY (Device or resource busy) ioctl(8, 0x4008642a, 0xbfdf4254) = 0 ioctl(8, 0xc0046444, 0xbfdf41f4) = 0 gettimeofday({1150330312, 398179}, NULL) = 0 sched_yield() = 0 ioctl(8, 0xc0046444, 0xbfdf42c4) = 0 Looks like the wait for vblank ioctl is timing out... Are you setting vblank_mode in ~/.drirc or /etc/drirc? Does it work if setting the environment variable vblank_mode=0? I didn't have a drirc. After creating one and setting vblank_mode to 0, the problem remains. $ cat .drirc <driconf> <device screen="0" driver="i915"> <application name="Default"> <option name="force_s3tc_enable" value="false" /> <option name="fthrottle_mode" value="2" /> <option name="vblank_mode" value="0" /> <option name="allow_large_textures" value="1" /> </application> </device> </driconf> $ LIBGL_DEBUG=all googleearth libGL warning: 3D driver claims to not support visual 0x4b Mesa: CPU vendor: GenuineIntel Mesa: CPU name: Genuine Intel(R) CPU T2300 @ 1.66GHz Mesa: MMX cpu detected. Mesa: SSE cpu detected. Mesa: Not testing OS support for SSE, leaving enabled. libGL error: Can't open configuration file /etc/drirc: No such file or directory. do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try running with LIBGL_THROTTLE_REFRESH and LIBL_SYNC_REFRESH unset. I guess you have a laptop ? If so, then the irq's are not configured correctly. You need to get the latest 1.6.5 driver as well as the latest DRM sources for the kernel driver i915.ko. (In reply to comment #6) > I guess you have a laptop ? > Yeah. > If so, then the irq's are not configured correctly. > > You need to get the latest 1.6.5 driver as well as the latest DRM sources for > the kernel driver i915.ko. OK, that did it. No more errors, and googleearth now loads fine. Great, thanks! (In reply to comment #6) > I guess you have a laptop ? > > If so, then the irq's are not configured correctly. > > You need to get the latest 1.6.5 driver as well as the latest DRM sources for > the kernel driver i915.ko. Hello, Can you please explain how to do this step by step? I have installed Ubuntu only a few weeks ago and I have not much experience. Thank you! Whoa, this is an *old* bug. I think it's fixed too. Ricardo or Walter, please reopen if you still see this issue with recent versions of the driver. |
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.