I updated my home server with the 6.4 CR packages, and I've experienced 3 or 4 hard lockups since. The server is a fanless VIA C7 "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, but doesn't currently have an IP address configured.) This server provides a number of services -- DNS, DHCP, routing between VLANs, DLNA media server, CUPS, etc. Most importantly, it runs Asterisk and manages all of the phones in the house. There's absolutely nothing in the logs related to the lockup. The system simply becomes totally unresponsive, to the point that the console cursor stops blinking. A hard reset is required to bring it back. kernel-2.6.32-279.22.1.el6.i686 seems to be completely stable. I don't really expect to be able to figure this out, but I thought I'd post here to see if anyone else is experiencing anything like this with this kernel. Thanks! -- =======================================================================Ian Pilcher arequipeno at gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher <arequipeno at gmail.com> wrote:> I updated my home server with the 6.4 CR packages, and I've experienced > 3 or 4 hard lockups since. The server is a fanless VIA C7 > "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of > RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It > also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, > but doesn't currently have an IP address configured.) > > This server provides a number of services -- DNS, DHCP, routing between > VLANs, DLNA media server, CUPS, etc. Most importantly, it runs Asterisk > and manages all of the phones in the house. > > There's absolutely nothing in the logs related to the lockup. The > system simply becomes totally unresponsive, to the point that the > console cursor stops blinking. A hard reset is required to bring it > back. > >I'm running 2.6.32-358.0.1 on a KVM virtual machine and not seeing any issues. I've not yet ran that kernel on physical hardware yet though.> kernel-2.6.32-279.22.1.el6.i686 seems to be completely stable. > > I don't really expect to be able to figure this out, but I thought I'd > post here to see if anyone else is experiencing anything like this with > this kernel. > > Thanks! > > -- > =======================================================================> Ian Pilcher arequipeno at gmail.com > Sometimes there's nothing left to do but crash and burn...or die trying. > =======================================================================> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- ---~~.~~--- Mike // SilverTip257 //
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher <arequipeno at gmail.com> wrote:> > I updated my home server with the 6.4 CR packages, and I've experienced > 3 or 4 hard lockups since. The server is a fanless VIA C7 > "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of > RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It > also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, > but doesn't currently have an IP address configured.)Wow. I'm trying to troubleshoot a very similar problem. I was convinced that it was hardware, but beginning to exhaust my hardware troubleshooting skills. I'm running an Asus M5a99X EVO 2.0, Asus Geforce GTX 660, and AMD 8150 CPU, 32G RAM, Corsair 850W PS. Randomly I get a complete lockup. Mouse freezes, network dies, etc..> There's absolutely nothing in the logs related to the lockup. The > system simply becomes totally unresponsive, to the point that the > console cursor stops blinking. A hard reset is required to bring it > back. > > kernel-2.6.32-279.22.1.el6.i686 seems to be completely stable.Same here. No log messages, just a complete freeze. At first I was suspecting some Pulseaudio glitches because of thousands of messages in the log. Then suspected the proprietary NVidia graphics, then thought it might be power supply. I've since swapped out every component with no improvement. It can sometimes for for hours without a problem, sometimes with a minute after a reboot it will lock up. Have you enabled your thermal sensors? Do you have any messages in the kernel log?
On 03/08/2013 11:46 AM, Kwan Lowe wrote:> On Fri, Mar 8, 2013 at 11:34 AM, <m.roth at 5-cent.us> wrote: >> Ok, so there was nothing in /var/log/dmesg? Have you tried running mcelogd? > Nothing in dmesg, but I have not run mcelogd. I will try that tonight. Thanks! > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >Run memtest on your memory and leave it running overnight. .
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher <arequipeno at gmail.com> wrote:> I updated my home server with the 6.4 CR packages, and I've experienced > 3 or 4 hard lockups since. The server is a fanless VIA C7 > "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of > RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It > also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, > but doesn't currently have an IP address configured.)Well.. Looks like my hardware problems were only superficially the same as yours. After fighting it for two weeks, I got the second replacement motherboard in on Tuesday. Swapped it out and it has been rock solid stable since then. At some point I may try bringing up the BIOS to the same version as on the failed board if someone has a similar problem, but for now it's staying at the back rev version.
Running kernel-2.6.32-358.2.1.el6.i686 for a couple of days now with no problem. <knock on='wood'/> -- =======================================================================Ian Pilcher arequipeno at gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================