[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 261323] Flip Switch causes desktop to become unresponsive
From:       Thilo-Alexander Ginkel <thilo () ginkel ! com>
Date:       2011-04-24 11:19:42
Message-ID: 20110424111942.3D5538637C () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=261323





--- Comment #70 from Thilo-Alexander Ginkel <thilo ginkel com>  2011-04-24 13:19:40 ---
(In reply to comment #67)
> a) the logs suggest that thilo's using indirect rendering and ralph uses direct
> rendering - confirmed? in case:
> @thilo: does indirect rendering still work around the flipswitch? (but not the
> cube issue)

Most of the time. I hit the freeze after making some effects changes (where
even disabling DRI does not always help).

BTW, considering that your system is a single-core CPU, I tested the hypothesis
that a multi-core CPU is required to trigger the issue. Seems that this
hypothesis is correct as disabling all but one core (using maxcpus=1 on the
kernel command line) makes the freezes go away (even with DRI and VSync
enabled). However, I still get the nVidia Xid kernel log entries where I would
usually have gotten a freeze:

NVRM: Xid (0001:00): 13, 0003 00000000 00008297 00000f10 44960000 00000040

@All: Is there anyone, who is getting these freezes with DRI enabled and only a
single(-core) CPU?

@Thomas: If you - by chance - have an Intel socket 775 mainboard, let me know -
I have some spare dual-core hardware available that I could lend you to aid
debugging.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]