You are not logged in.
Pages: 1
After installing kernel 3.12.6, I've had two hard locks that've occurred in the early morning hours when the terminal was not in use by an operator. These seem to be true hard locks; if the monitors are asleep, they do not wake on input, and if they are awake, they never go to sleep and the image stays frozen as it was at lock time. No input seems to be interpreted. I haven't tried sysrq escape sequences yet.
The log provides no unusual mark at all, it just quits when the system locks.
I've connected no new peripherals or hardware and changed no settings. Simply reboot to begin running the new kernel. Will revert to 3.12.5 to prevent the problem and report back if this turns out not to be the issue.
P8Z77-V Deluxe / 3770K
GTX 670 with nvidia 331.20
32GB RAM
Last edited by cookiecaper (2014-01-01 19:25:49)
Offline
Kernel 3.12.5 had the same issue. I reverted to 3.12.4 and seem to be OK.
It came to my attention that another machine I maintain has encountered similar hard locks since upgrading to 3.12.6. It seems to have happened much more frequently on that machine, with multiple hard locks per day. That machine is rather different from the machine I'm currently running (i686 v. x64, AMD proc v. Intel, etc.), but they both run the nvidia blob (though the other machine runs nvidia-304xx) -- I think it is the most likely suspect for the source of the incompatibility.
I may bisect soon if I have time. Nobody else is experiencing this? I'm surprised not to see more reports.
Offline
Pages: 1