Are you sure you're running RHEL 5.x and not 4.x? [jnesheim at las-admin ~]$ uname -a Linux las-admin.smartvoice.telepacific.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux [jnesheim at las-admin ~]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.3 (Tikanga) 5.x should be on 2.6.18 where 4.x is 2.6.9. You also should be using yum to do updates on 5.x instead of up2date. -- Jason Nesheim ----- Original Message ----- From: "Ujjval Karihaloo" <ujjval at simplesignal.com> To: "Alex Balashov" <abalashov at evaristesys.com>, voiceops at voiceops.org Sent: Saturday, January 9, 2010 8:43:00 AM Subject: Re: [VoiceOps] RHEL nm watchdog kernel panic Going through that since last night... A lot of NMI bug fixes are in RH Kernel 2.6.18 apparently, however, up2date -u from RH website only updates to 2.6.9 and their website is currently down too...so I cannot confirm if they actually have a 2.6.18 for our RHEL server -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Saturday, January 09, 2010 9:25 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] RHEL nm watchdog kernel panic On 01/09/2010 08:20 AM, Ujjval Karihaloo wrote:

Has anyone seen a broadsoft server on a ibm blade center running RHEL 5.x crash with this error

Kernel panic not syncing nmi watchdog

A simple Google search would have much to say on the subject. -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

On Mon, Jan 11, 2010 at 7:36 PM, Ujjval Karihaloo <ujjval at simplesignal.com> wrote: NMI watchdog panics can be caused by a number of things, primarily kernel deadlock, or machine check exceptions. The log output of a panic you got _should_ be more detailed than just 'NMI watchdog' message. 'NMI watchdog' is just the name of the error detection method that provided the panic message.

Yes, it is 4.x, my bad. Ujjval Karihaloo

Then you might want to gather some details (especially, how to reproduce it) and create a support incident with Redhat, to request technical assistance/a workaround regarding that ancient kernel, or find means to migrate to a newer major release that isn't so ancient. e.g. To gather info, setup RH4 'netdump' and 'netconsole'. Have more detailed logs and a kernel crashfile dumped to another server over syslog and ssh netdump user, in case of another lockup. In early 2.6 kernels such as the 2.6.9 kernels used by RH4, there were some deadlock issues that could cause this. RH 4.x is now in the last phase of RH4's production support life cycle, according to Redhat support policy has just a little more than 2 years left. No new minor releases or new hardware enablement are expected, only certain security errata and mission critical bugfixes. The issue may need to be reported to Redhat, by a customer, before they will look into a bugfix.... -- -J