Andy Furniss changed bug 84662
What Removed Added
Status RESOLVED REOPENED
Resolution FIXED ---

Comment # 40 on bug 84662 from
(In reply to Michel Dänzer from comment #39)
> Resolving, please reopen if there are remaining issues with the Elemental
> demo.

It's still not right for me and never has been.

I haven't had much time to test recently, but what testing I did it seems that
some of it may be when it loads from disk/disk cache. Maybe because I only have
4G RAM it's worse for me - but then I don't know why it still messes up from
cache.

Last night I updated kernel to agd5f 3.19-wip and current mesa, after applying
the mesa patches I got a lockup/crash. I hadn't retarted X though so glamor was
using vanilla. I didn't crash instantly - first run was OK, and I haven't had
time yet to see if it's just something new with different mesa/kernel, or if
the patches + 3.19 are the cause.

Are the mesa patches still valid?

I'll attach the log, initially it was just that elemental didn't start, I was
still OK, could switch desktops and use top to see it was maxing a single core,
after a while I tried to start sysprof, which segfaulted, after that I was
unstable eg. free hung and I tried to quit X but hung then I SysRqd.


You are receiving this mail because: