Comment 7 for bug 315819

Hmm. Somehow I managed to miss all the X errors :-).

I'm not sure about your logic though. The logfile seems to contain output for 3 different runs of the X server. If you're right, we are interested in the last two runs. But *all* of them end in this same X error.

The *difference* between the last two runs is the error from kdmgreet in the second run:

kdmgreet: Fatal IO error: client killed
error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)
 ddxSigGiveUp: Closing log

Surely that kdmgreet error is what you would expect to happen just after ctrl+alt+backspace. So it's not restarting X?

The other alternative is that kdmgreet is silent in response to ctrl+alt+backspace, but when it tried to restart X, something *other* than the MTRR error went wrong, which X did not log an error for, and kdmgreet then died.

Also, as far as I know it's not a fatal error to fail to setup an MTRR. It just slows things down :-). So I think the MTRR error is unlikely to be related to a crash.

Finally, X crashes are normally a bit spectacular - you at least see the screen flicker or something. I didn't see anything like that, it *looks* as if X just dies and is not restarted.