http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #21 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-25 04:48:47 --- (In reply to comment #20)
I've had a bit of success with ME2 by stopping the cpufrequtils daemon, that is "sudo service cpufrequtils stop". I also added the grub boot option "clock=notsc" to my system, I'm not sure if that played a part or not. Note that notsc is for 64 bit systems, "clock=pit" might work for you. Again, I'm not sure it played a part in the outcome.
Mass Effect 2 seems to work quite well this way, and I think that cpufrequtils does not affect much when disabled in any case. So it seems clear that ME2 doesn't like cpu frequency adjustments being done mid-game. If there's any way to correct this other than what I've gone over here, I'd really like to know.
To be clear about "clock=pit", that's for 32 bit systems.