We still cannot resolve the issue and it occurs with DL380p Gen 8 8-core and 12-core models.The HBA on the riser card fails. Subscribing... https://bugs.launchpad.net/bugs/1432840 Title: The update process become buggy with many enabled repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1432840/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs Previous Message by Thread: [Bug You are right, I already found this also. have a peek at these guys
intel_idle+0xe7/0x160 [ 5493.592448] [
The kernal panic I see only happens while the VM is starting and CPU load sky rockets. So it is strongly advised that all Ubuntu Trusty Servers, running Xeon® Processor E7 v2, to be upgraded "at least" to kernel 3.13.0-35". This probably falls on HP first. If you go back to the 4.1 or 3.9 kernel on the HP does the issue go away? #13 adamb, Nov 11, 2015 pipomambo New Member Joined: Nov 11, 2015
Reason: Added link to the HP forum Ser Olmy View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Ser Olmy 06-02-2014, 06:33 AM If you'd like to contribute content, let us know. I've got HP DL320e Gen8 v2 and Your solution works for me. An Unrecoverable System Error (nmi) Has Occurred (service Information: 0x7fbce8f6, 0x00000000) 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)
Help answer threads with 0 replies. An Unrecoverable System Error Nmi Has Occurred Dl585 Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ The issue occurs most often when we use live migration. i thought about this You are currently viewing LQ as a guest.
iLO Event Log [ 5492.505988] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.0-123.9.2.el7.x86_64 #1 [ 5492.605615] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 08/02/2014 [ 5492.692636] ffffffffa03ae2d8 17844fa82b224426 ffff880fffa06de0 Ilo Watchdog Nmi In some ways, the VM stop and start... With the module hpwdt loaded, a kernel panic happens randomly. We have provided the following cmdline to be used: " intel_idle.max_cstate=0 ".
Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Members Members Quick Links Notable Members Current Visitors Recent Activity New Profile Posts Menu Log in Sign up This Issue is not a Proxmox VE one. #4 t.lamprecht, Oct 21, 2015 mensinck New Member Joined: Oct 19, 2015 Messages: 4 Likes Received: 0 Hi t.lamprecht t.lamprecht said: ↑ An Unrecoverable System Error Nmi Has Occurred Hp Rafael David Tinoco (inaddy) wrote on 2015-04-07: #12 Checked /lib/modprobe.d/blacklist_linux_* on Precise, Trusty, Utopic and Vivid and all of the contain hpwdt being blacklisted. An Unrecoverable System Error (nmi) Has Occurred Proliant Learn More Red Hat Product Security Center Engage with our Red Hat Product Security team, access security updates, and ensure your environments are not exposed to any known security vulnerabilities.
https://bugs.launchpad.net/bugs/1432837 Title: HP Proliant Servers - Kernel Panic - NMI - DL360 & DL380 - HPWDT module loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837/+subscriptions -- ubuntu-bugs mailing list http://lanprolab.net/an-unrecoverable/an-unrecoverable-system-error-nmi-has-occurred-system-error-code.php Forum software by XenForo™ ©2010-2016 XenForo Ltd. proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-50 (running version: 4.0-50/d3a6b7e5) pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1 libqb0: 0.17.2-1 pve-cluster: 4.0-23 qemu-server: 4.0-31 pve-firmware: 1.1-7 libpve-common-perl: 4.0-32 libpve-access-control: 4.0-9 libpve-storage-perl: 4.0-27 pve-libspice-server1: but it's a bit different, you are right. #14 pipomambo, Nov 11, 2015 adamb Member Proxmox VE Subscriber Joined: Mar 1, 2012 Messages: 777 Likes Received: 3 pipomambo said: ↑ An Unrecoverable System Error Has Occurred Error Code 0x0000002d 0x00000000
intel_idle+0xe7/0x160 [ 5493.663438] [
I installed the patch one month ago and still now everything works properly. Ilo Application Watchdog Timeout Nmi Service Information 0x0000002b 0x00000000 Newer Than: Search this thread only Search this forum only Display results as threads More... If you have any questions, please contact customer service.
HP was advised by Canonical regarding Intel Errata # and that recommended workaround is a fix in firmware. NMI's will be logged as Unrecoverable System Errors something like this: An Unrecoverable System Error has occurred (Error code 0x0000002D, 0x00000000 The first 32-bit error code can be decoded using this Do you have all the HP management agents installed and running? Uncorrectable Pci Express Error Bad motherboard.
Code: echo "A" > /dev/watchdog This should reset the machine after a bit. Below the used command lines to add certain repositories which cause the problem. ---------------------------------- sudo su echo deb http://archive.getdeb.net/ubuntu utopic-getdeb apps >> /etc/apt/sources.list && echo deb http://archive.getdeb.net/ubuntu utopic-getdeb games >> /etc/apt/sources.list sched_clock+0x9/0x10 [ 5493.224869] [
We have a cluster on Proxmox V4.0-48 with two Dell R900 and one HP DL380 G9. Need access to an account?If your company has an existing Red Hat account, your organization administrator can grant you access. Changed in linux (Ubuntu Utopic): status: Fix Committed → Fix Released See full activity log To post a comment you must log in. For the HP was a known problem.
Doing Code: echo "A" > /dev/watchdog with watchdog-service off (kernel module hpwdt.ko blacklisted), as well as Code: echo "A" | socat - UNIX-CONNECT:/var/run/watchdog-mux.sock with service activated will reboot the server now. Password Linux - General This Linux forum is for general Linux questions and discussion. Trying to continue.Mar 23 08:19:31 vmw8 kernel: You probably have a hardware problem with your RAM chips.Mar 23 08:19:31 vmw8 kernel: Please consult hardware error logs.Mar 23 08:19:31 vmw8 hpasmd: CRITICAL: Rafael David Tinoco (inaddy) wrote on 2015-04-07: #11 Doing verification right now...
GBiz is too! Latest News Stories: Docker 1.0Heartbleed Redux: Another Gaping Wound in Web Encryption UncoveredThe Next Circle of Hell: Unpatchable SystemsGit 2.0.0 ReleasedThe Linux Foundation Announces Core Infrastructure Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search This is why I suspected the USB drives.We already had a systemboard replacement and after that the freqency went up.