| Summary: | XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 4294967296 requests (4294967294 known processed) with 0 events remaining. | ||
|---|---|---|---|
| Product: | xorg | Reporter: | me4xorg |
| Component: | Lib/Xlib | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | BlanchardJ |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | 2011BRB_Reviewed | ||
| i915 platform: | i915 features: | ||
... yeah ... 3 months though... not bad. I am new to this forum, so this may not be the correct place to post this but...I have the same problem...only this happens after about 2 days time. This is a real time system and it needs to run for more than 2 days. I am on a linux box (redhat 2.6.32-131.6.1.el6.x86_640) with Nvidia GE Force GTX 460M, driver 280.13). Has this bug been fixed? Is there a way to resolve this issue? Thank you. Any help would be greatly appreciated! This is also reproducible for me (SuSE 12.2 ) Name : libX11-6 Version : 1.5.0 Release : 2.7.1 Architecture: i586 Install Date: Mon 21 Oct 2013 06:36:51 PM CEST Group : System/Libraries Size : 1281072 License : MIT Signature : RSA/SHA256, Wed 19 Jun 2013 11:58:45 AM CEST, Key ID b88b2fd43dbdc284 Source RPM : libX11-1.5.0-2.7.1.src.rpm Build Date : Wed 12 Jun 2013 09:52:25 AM CEST *** This bug has been marked as a duplicate of bug 71338 *** |
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.
beryl (ancient composite window manager) has crashed after a long uptime (~96days) leaving this message in the console: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 4294967296 requests (4294967294 known processed) with 0 events remaining. the error was not fatal (beryl started fine without restarting X) but the number of requests (2^32) made me curious (not initialized or really hit a boundary). you can review the details of my configuration here: http://pastebin.com/e2MxCaXf i'm using x2x to control this display (maybe thats where the large amount of events comes from) i'm not sure how to reproduce the bug. the current office temperature or the long uptime could be indicators. the system was left alone over the weekend, so no user-interaction was done.