Hi there, I have a Intel DQ67EP mainboard with a Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, and Gentoo Linux OS. On this OS I run a fullscreen opengl application (using QT), and I have an external process that reboots this app periodically. I have some problems to make the videocard working well, I have tested many drivers and combination, but all of these have some troubles: with 2.6.38.8 kernel, x-server 1.10.4, mesa 7.10.3, libdrm 2.4.25, xproto 7.0.22 and Intel 2.15.0, , when my app reboots, I have random X crash, with no output, but X stops working. with 3.0.4 kernel, x-server 1.11, mesa 7.11, libdrm 2.4.26, xproto 7.0.22, seems workin well, but I have a crash rotation monitor with xrandr (xrandr -o right crashes the system) with 2.6.38.8 kernel, x server 1.10.4 mesa 7.10.4, intel driver from git (18/10/2011), xproto 7.0.22, xrandr rotation works well, I have fewer crash on X, but still sometimes having some crash. So, I think that my CPU/video works badly with 2.15.0, than I have a regression in 2.16.0 with rotation feature, and then with last git driver, my system works better but isn't fully functional yet. I have any difference changing kernel, or Xserver, or Mesa or another component, How can I resolve this problem? What's the most stable config for my system? Thank you
We need a lot more specific information on your issues before we can even begin to identity your problems. Please see http://intellinuxgraphics.org/how_to_report_bug.html for a guide on the information we need. In this case, dmesg, Xorg.log and i915_error_state following a crash would be the best start.
Hi In addition to the information requested by Chris, please answer the following question: - Is the "qt fullscreen application" the *only* application you're running under X? (I mean: no desktop environment at all, no window manager, no meny bar, anything) If yes, consider adding the "-noreset" option to the X server and see if anything changes. Answering your questions: for SandyBrdige, the recommended is to always use the latest versions.
Timeout. Please do reopen if you can still reproduce the issue and help us diagnose the problem, thanks.
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.