> X freezes are usually just important, adjusting. I think this makes X completely unusable, but whatever, I am not the boss. =) > > It started probably after upgrading to 2:2.9.1 (I cannot be sure). > What about downgrading to see whether that happened back then already? > It might be nice to see whether that's “just” a regression from a > known-working version. The testing/squeeze version certainly has the same problems: I downgraded from that version earlier back to 2.9.0 because of that, but mistakenly upgraded later and now I do not have 2.9.0 anywhere any more (besides I think 2.9.0 needs an older X core as well etc). I could give a try to 2:2.10.903-1 from experimental, though... > Could you also give the 2.6.32-4-$arch kernel from sid a try? It might > have some DRM-related fixes (backported from 2.6.33 and maybe later), > which may help. Unless you tell me that the iwlagn-memory-reservation-bug is also backporter into .32-4, I will not. That was as annoying as this. (See https://bugzilla.kernel.org/show_bug.cgi?id=14141 for details.) On a second thought... that caused no data loss, this does... I will upgrade to the latest .33 first (along with that 2.10.903). Cheers, Juha -- ----------------------------------------------- | Juha Jäykkä, juhaj@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | -----------------------------------------------
Attachment:
signature.asc
Description: This is a digitally signed message part.