Using Core i7 boxes with CentOS 5.7, have experienced lockups on half of a handful of units over a couple months. They are Logic Supply Mini-ITX model KR960 with Core i7-3610QE.
A couple weeks ago I enabled self-reboot on kernel panic (echo 10 > /proc/sys/kernel/panic) on all units, and had another unit lock up rather than reboot itself.
I'm not sure how to pursue the problem.
Doing "yum update kernel*" shows there's a newer kernel, 2.6.18-371.1.2.el5 - I'm using the stock 2.6.18-274.el5 kernel now - where's a change log of the differences so I can see if there are driver or kernel updates that might seem to apply?
I don't know if setting up kdump would help since it doesn't even seem to be getting to the point where the kernel is trying to handle a panic.
What else might I try?
John R Pierce pierce@hogranch.com wrote:
On 11/16/2013 9:50 PM, whitivery wrote:
What else might I try?
centos 6.latest ? or at least 5.latest.... 5.7 is circa 2011, there's dozens of kernel patches since then, its up to 5.10 now.
Thank you John and John for the replies.
I was guessing that doing a kernel update on CentOS 5.7 would get me the most critical patches like 5.10 has but maybe not.
I was going for the kernel update since it could be done with a few RPMs remotely, fairly safely. I'm not sure if the same can be done with 5.7 to 5.10 or 6.4.
On 11/18/2013 12:08 AM, whitivery wrote:
I was going for the kernel update since it could be done with a few RPMs remotely, fairly safely. I'm not sure if the same can be done with 5.7 to 5.10 or 6.4.
5.7 should upgrade to 5.10+ painlessly. if the host doesn't have internet access, you can useyum with a mirror of the public repositories, like everything in centos/5/updates/x86_64/ or whatever,
On Sat, Nov 16, 2013 at 09:50:49PM -0800, whitivery wrote:
What else might I try?
Updating to something supported? Current in the 5 series is 5.10; 5.7 has been unsupported for quite some time now.
John
-
John R Pierce -
John R. Dennison -
whitivery