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?
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. -- john r pierce 37N 122W somewhere on the middle of the left coast
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 -- "When we remember we are all mad, the mysteries disappear and life stands explained." -- Mark Twain -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20131117/8c7ccbb2/attachment-0004.sig>
Possibly Parallel Threads
- CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
- Cannot %include in CentOS 5.5 kickstart
- CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
- CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
- CentOS 5.7 Ethernet bonding - order of enslavement matters?