Comment 8 for bug 328035

Good to hear the text console issue has gone away. Issues with text consoles can sometimes be kernel issues; if it went away after upgrading the kernel, then that would be a pretty strong clue. We've not put in any changes to -intel recently that would have made that start working, and the only noteworthy xserver change was removing the maxclients change (which caused issues for -nvidia), although I'm doubtful that would have caused vt corruption. So, my guess there would be that either the issue is intermittent and will come back, or it was a kernel issue that is now fixed.

> However, this backtrace will only be for the free(3) which triggers the abort.
> If my guess is right, then the corruption is happening sometime earlier, and
> may be very difficult to track down. Does the X server play nicely with valgrind?

valgrind is definitely listed as an X testing tool (http://freedesktop.org/wiki/Software/XTesting) although I've tried running it myself and it just makes X flicker and turns my vt consoles yellow. It certainly flags a lot of issues, though. If you can get X to run under it enough to reproduce the issue, maybe it could give us useful info.