On Tue, Jan 26, 2010 at 08:09:27PM +0200, Yoav Luft wrote: > ok, it happened in X, and happened several times. I suspect it happens > only when the screen is supposed to go to standby, but it's only > suspicion, not a fact. I've changed the kernel settings lately, > without installing the new kernel yet, and I'm about to do that now, > with magic SysReq, just in case. > I'm not sure if the system is really ideal, or just that application > are unresponsive. > While writing this mail I've managed to recreate the symptoms by > pressing ctrl+alt+F1. I have an intel video card, and remember having > some problems with it. > > What log should I check? I never tried to track down this kind of > error in the past.
kernel log, maybe. (If you use metalog, the default should be under /var/log/kernel/) X log (/var/log/Xorg.?.log) If your computer has sshd open, you can try to ssh-in from another computer. If you can get in, at least you don't have a full-blown kernel panic. What kernel settings did you tweak? Installed a new kernel maybe? Which kernel version? With an intel video card, are you using kernel mode setting? Do you have a "previous" kernel where everything is working? If so, what are the diffs between the configs? [Yes, a situation like this is why it is nice to either save your kernel configs or save the old bzimage with /proc/config.gz enabled.] Cheers, W -- Willie W. Wong [email protected] Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
