Removing the watchdog is not a proper solution. If the OS locks up hard, watchdog timers (if configured) would eventually trigger an NMI. Edit: Have you seen this thread? Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log https://access.redhat.com/solutions/1309033
That's why I wrote that our systems runs SLES 11 with sp2. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. As described in /etc/modprobe.d/blacklist-watchdog.conf: """ # Watchdog drivers should not be loaded automatically, but only if a # watchdog daemon is installed. """ We should blacklist module "hpwdt" by default for Systems are crashing with following panic message: [ 5492.146364] Kernel panic - not syncing: An NMI occurred.
Last edited by Ser Olmy; 06-02-2014 at 05:03 AM. SCSI hang ? Of course we shall recommend the HW watchdog interface for 2 node cluster setups, for example, when we can't rely on quorum policies and fencing mechanisms are not available (like external Ilo Application Watchdog Timeout Nmi Service Information 0x0000002b 0x00000000 Red Hat Customer Portal Skip to main content Main Navigation Products & Services Back View All Products Infrastructure and Management Back Red Hat Enterprise Linux Red Hat Virtualization Red Hat Identity
The time now is 06:39 AM. Uncorrectable Pci Express Error Dl380p Gen8 Soadyheid View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Soadyheid 09-22-2014, 04:48 AM #7 kaito.7 LQ Newbie Registered: Jun 2014 Posts: Since then I monitor the hardware from Onboard Administrator and there is no something strange. I checked all the logs (/var/log/messages, crash, etc.) and i did not find something usefull to understand the reason of the fail.
Try removing them.3. http://lanprolab.net/an-unrecoverable/an-unrecoverable-system-error-nmi-has-occurred-system-error-code.php ILO: "76 CriticalSystem Error03/12/2015 12:4203/12/2015 12:072 An Unrecoverable System Error (NMI) has occurred (System error code 0x0000002B, 0x00000000)" Examples: PID: 0 TASK: ffffffff81c1a480 CPU: 0 COMMAND: "swapper/0" #0 [ffff88085fc05c88] machine_kexec at Need access to an account?If your company has an existing Red Hat account, your organization administrator can grant you access. tags: added: verification-needed-precise tags: added: verification-needed-trusty Brad Figg (brad-figg) wrote on 2015-03-26: #9 This bug is awaiting verification that the kernel in -proposed solves the problem. Ilo Watchdog Nmi
Although there are updates to your version of VCA: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=397646&swItem=MTX-79ef5fa4197944f99c4cd1c4c6&prodNameId=3279717&swEnvOID=1005&swLang=8&taskId=135&mode=5 Almost anything can cause an ASR. Disable the ASR (for testing only)4. Check the system event logs since those error codes aren't getting any hits... news Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you need to reset your password, click here. Kernel Panic - Not Syncing: An Nmi Occurred intel_idle+0xe7/0x160 [ 5493.592448] [
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
Report a bug This report contains Public information Edit Everyone can see this information. The system runs SLES 11 with sp2. sched_clock+0x9/0x10 [ 5493.224869] [
Blacklisting the watchdog timer just hides underlying problems. Changed in linux (Ubuntu Trusty): status: Fix Committed → Fix Released Launchpad Janitor (janitor) wrote on 2015-04-08: #14 This bug was fixed in the package linux - 3.2.0-80.116 --------------- linux (3.2.0-80.116) In addition, I think there is a second problem here. More about the author Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log
Search this Thread 06-02-2014, 03:17 AM #1 kaito.7 LQ Newbie Registered: Jun 2014 Posts: 6 Rep: BL460c G8 host unexpectedly reset Hi all, We have a HP BL460c G8 When the watchdog fires, I expect that we should provide the end user good diagnostic information so they know it was a watchdog timeout. Anyone can find instructions on how to run it here: https://github.com/inaddy/notifymydog Small Example: [email protected]:~$ wget https://raw.githubusercontent.com/inaddy/notifymydog/master/notifymydog.c [email protected]:~/notifymydog$ gcc -Wall -D_DEBUG=0 -D_SYSLOG=1 notifymydog.c -o notifymydog [email protected]:~/notifymydog$ sudo ./notifymydog & [email protected]:~$ sudo tail early_idt_handlers+0x120/0x120 [ 5494.343686] [
LinuxQuestions.org > Forums > Linux Forums > Linux - General BL460c G8 host unexpectedly reset User Name Remember Me? repair_env_string+0x5c/0x5c [ 5494.262390] [