Bug 26845 - Using wine causes system to become unresponsive
Summary: Using wine causes system to become unresponsive
Status: RESOLVED DUPLICATE of bug 49906
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Eugeni Dodonov
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-02 10:50 UTC by Clemens Eisserer
Modified: 2012-10-14 21:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Syslog after using wine (21.65 KB, text/plain)
2010-03-02 10:50 UTC, Clemens Eisserer
no flags Details
xorg log after using wine (63.48 KB, application/octet-stream)
2010-03-02 10:51 UTC, Clemens Eisserer
no flags Details
lspci output (1.79 KB, text/plain)
2010-03-02 10:52 UTC, Clemens Eisserer
no flags Details
Cache EDID probes (2.49 KB, patch)
2010-03-02 11:04 UTC, Chris Wilson
no flags Details | Splinter Review

Description Clemens Eisserer 2010-03-02 10:50:55 UTC
Created attachment 33692 [details]
Syslog after using wine

After starting graphical windows applications using wine (or even wine-based applications like winecfg) my system becomes unresponsive for about 30s-5min.

During this time mouse-movement is jerky and applications aren't painted and don't react at anymore.
This happens with intel-2.10.901, but did also happen with intel-2.9.1 on my system.

happens with
- kernel-2.6.32.9-67.fc12.i686
- intel-2.10.901 (but also with 2.9.1)
- FC12 + updates-testing
Comment 1 Clemens Eisserer 2010-03-02 10:51:20 UTC
Created attachment 33693 [details]
xorg log after using wine
Comment 2 Clemens Eisserer 2010-03-02 10:52:23 UTC
Created attachment 33694 [details]
lspci output
Comment 3 Clemens Eisserer 2010-03-02 10:54:05 UTC
Forgot to mention, this happens on my Toshiba-Tecra-A8 with i945GM.

After rebooting, the boot process takes unusual long with messages like:
"Invalid EDID" beeing displayed at startup several times.

To make this behaviour to go away, I have to completly power down (not reboot) the laptop.
Comment 4 Chris Wilson 2010-03-02 11:04:40 UTC
Created attachment 33695 [details] [review]
Cache EDID probes

I'm not sure what is causing the sudden onslaught of EDID probing, presumably it is hotplug gone mad, but why? And to make matters worse it seems like we trigger a h/w bug by probing too ofter?

This patch may help workaround the issue by caching the earlier EDID results.
Comment 5 Chris Wilson 2010-03-02 11:11:17 UTC
Also of relevance is the patch by Yakui to ignore invalid EDID results, c38 bug 23099: http://bugs.freedesktop.org/attachment.cgi?id=33486
Comment 6 Clemens Eisserer 2010-06-26 17:29:53 UTC
still happens with 2.6.34 + intel-2.12, but the blocking duration is now way shorter than it was and also syslog isn't flooded with "Invalid EDID" messages.

I made a vide moving konsole, while starting a wine application: http://www.youtube.com/watch?v=DKAFxS5DRx4
Comment 7 Clemens Eisserer 2012-01-27 09:31:03 UTC
jap, still there (2.17-git + linux-3.2.1)
Comment 8 Eugeni Dodonov 2012-04-09 07:39:27 UTC
Does it still happens with 3.4-rc2?
Comment 9 Clemens Eisserer 2012-04-12 15:07:15 UTC
Hi Eugeni,

It still happens with linux 3.3.1 - I'll give 3.4 a try when its released to fedora updates testing repo.
Comment 10 Clemens Eisserer 2012-04-13 01:12:33 UTC
just tested with 3.4_rc2, unfourtunatly the problem still persists
Comment 11 Chris Wilson 2012-05-11 06:45:29 UTC
Hmm, watching the movie... It looks like these problems could also be explained by UXA hitting software fallbacks (readbacks through the GTT), are the symptoms as severe with SNA?
Comment 12 Chris Wilson 2012-05-24 08:59:27 UTC
Assuming the bug is still present and not alleviated by SNA, it should be fixed by Daniel's reworking of hotplug detection.

*** This bug has been marked as a duplicate of bug 49906 ***
Comment 13 Clemens Eisserer 2012-10-14 21:08:34 UTC
Fixed, I can't reproduce the issue on kernel-3.6.1 + intel-git =)


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.