Scott Silva wrote on Thu, 13 Dec 2007 09:29:31 -0800:
You can temporarily move the new microcode, or just stop the microcode_ctl
program from running if you want to test that.
I already stopped microcode_ctl via chkconfig, but I have to wait a few days
before I go back to the new kernel to
Christopher Chan wrote on Thu, 13 Dec 2007 07:42:27 +0800:
I take it then that you do not have any third party modules then. In
which case, it will be just fine to reboot with an older kernel. Just
change the default entry set in grub.conf.
Changed last night and so far am fine. There's one
Kai Schaetzl wrote:
Christopher Chan wrote on Wed, 12 Dec 2007 22:28:24 +0800:
Hi Christopher, thanks for your reply!
May I ask whether the nature of your crashes involve network code?
No, it's likely more a filesystem issue. I posted earlier on the tenth in
the message unstable kernel
3 matches
Mail list logo
