<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Yes, it is 4.x, my bad.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ujjval Karihaloo<o:p></o:p></span></p>

</div>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jason L. Nesheim
[mailto:jnesheim@cytek.biz] <br>
<b>Sent:</b> Monday, January 11, 2010 5:45 PM<br>
<b>To:</b> Ujjval Karihaloo<br>
<b>Cc:</b> Alex Balashov; voiceops@voiceops.org<br>
<b>Subject:</b> Re: [VoiceOps] RHEL nm watchdog kernel panic<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'>Are
you sure you're running RHEL 5.x and not 4.x?<br>
<br>
[jnesheim@las-admin ~]$ uname -a<br>
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<br>
[jnesheim@las-admin ~]$ cat /etc/redhat-release <br>
Red Hat Enterprise Linux Server release 5.3 (Tikanga)<br>
<br>
5.x should be on 2.6.18 where 4.x is 2.6.9.<br>
<br>
You also should be using yum to do updates on 5.x instead of up2date.<o:p></o:p></span></p>

<div>

<div>

<div>

<p class=MsoNormal><span style='color:black'>-- <br>
Jason Nesheim<o:p></o:p></span></p>

</div>

</div>

</div>

<p class=MsoNormal><span style='color:black'><br>
<br>
----- Original Message -----<br>
From: &quot;Ujjval Karihaloo&quot; &lt;ujjval@simplesignal.com&gt;<br>
To: &quot;Alex Balashov&quot; &lt;abalashov@evaristesys.com&gt;,
voiceops@voiceops.org<br>
Sent: Saturday, January 9, 2010 8:43:00 AM<br>
Subject: Re: [VoiceOps] RHEL nm watchdog kernel panic<br>
<br>
Going through that since last night...<br>
<br>
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<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org] On
Behalf Of Alex Balashov<br>
Sent: Saturday, January 09, 2010 9:25 AM<br>
To: voiceops@voiceops.org<br>
Subject: Re: [VoiceOps] RHEL nm watchdog kernel panic<br>
<br>
On 01/09/2010 08:20 AM, Ujjval Karihaloo wrote:<br>
<br>
&gt; Has anyone seen a broadsoft server on a ibm blade center running RHEL<br>
&gt; 5.x crash with this error<br>
&gt;<br>
&gt; Kernel panic not syncing nmi watchdog<br>
<br>
A simple Google search would have much to say on the subject.<br>
<br>
-- <br>
Alex Balashov - Principal<br>
Evariste Systems<br>
Web &nbsp; &nbsp; : http://www.evaristesys.com/<br>
Tel &nbsp; &nbsp; : (+1) (678) 954-0670<br>
Direct &nbsp;: (+1) (678) 954-0671<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
https://puck.nether.net/mailman/listinfo/voiceops<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
https://puck.nether.net/mailman/listinfo/voiceops<o:p></o:p></span></p>

</div>

</div>

</body>

</html>