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 o
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 afte
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 after update to CentOS 4.5
Kai Schaetzl wrote:
As the latest 4.5 kernel (2.6.9-55.0.12.EL) is unstable for me (crashes
about once a day) I want to go back to the rock solid kernel that I had
before the update (2.6.9-34.0.2.EL). If nothing else then to confirm it's
not a kernel problem.
Are there any current packages tha
As the latest 4.5 kernel (2.6.9-55.0.12.EL) is unstable for me (crashes
about once a day) I want to go back to the rock solid kernel that I had
before the update (2.6.9-34.0.2.EL). If nothing else then to confirm it's
not a kernel problem.
Are there any current packages that might not work with
6 matches
Mail list logo
