On 2012-10-18 00:02, Jonathan Nieder wrote:
Per Foreby wrote:Correct, apart from the timing. It's been from a few hours to five days between the freezes. But with very little interactive use during the five days.Right --- how much interactive use does it take?
Very little. I've had freezes so far, and all of the with almost no activity on the screen. Clicking a link, typing an email or closing an rxvt window.
That should be cosmetic with your card, though there's always the possibility of something subtle happening.
As a rule of thumb, every bugfix in a complex enough system introduces another bug. So I suppose that sometimes a bugfux might accidentally fix another bug :)
With up to five days (so far) for a freeze to occur, it might take long to narrow down the change, and the computer in question is semi production (working from home), so the freezes are very annoying. But I'll give it a try in the name of the good cause. Maybe I should start with running 3.5.5 for a few weeks, just to make sure that the freezes really are gone?Selfishly, I would suggest first trying to reproduce it on a known-bad kernel and then trying 3.3 or disabling the intel driver.
OK, I'll go back to 3.2.23 and work my way up. It might take some time though if the freeze doesn't behave...
If you blacklist the i915 kernel module and use the vesa X driver, does that avoid trouble?
Does the vesa driver support 1920x1200 these days? /Per