** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI occurred, please see
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI occurred, please see the Integrated
Management Log for
Check this out:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417580
** This bug is no longer a duplicate of bug 1417580
HP Proliant Servers Advices for Ubuntu Linux (cmdline, panics, firmware
options)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
Wow.
I just spent the last 6 hours trying to solve this problem on a
supermicro machine (mother board is Supermicro X9SRL-F
http://www.supermicro.com/products/motherboard/Xeon/C600/X9SRL-F.cfm)
before
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
Maxim,
Good to know you are able to reproduce this behaviour and that you found
a workaround. When you say noautogroup fixed the problem.. was you
problem kernel panics due to NMIs ? Could you share stack
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
Maxim,
Also, if possible, could you follow http://www.inaddy.org/mini-
howtos/dumps/using-ubuntu-crash-dump-with-kdump instructions, enabling
kdump, and send me the core dump from /var/crash ? It looks
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
Check case:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837
If you ever face NMIs on Proliant Servers for no apparent reason.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
Whenever facing NMIs on Proliant Servers check NMI code under ILO:
Translate the code:
00h (0x) No source found
01h (0x0001) Uncorrectable Memory Error
1Bh (0x001B) ASR NMI
20h
*** This bug is a duplicate of bug 1417580 ***
https://bugs.launchpad.net/bugs/1417580
** This bug has been marked a duplicate of bug 1417580
HP Proliant Servers should use proper cmdline to avoid kernel panics
--
You received this bug notification because you are a member of Kernel
In order to better debug firmware issues can those affected by this
issue do the following:
1) sudo apt-get install fwts
2) sudo fwts
3) append 'results.log' to this bug
If that doesn't work you can also just produce an acpidump using the
following:
1) sudo acpidump acpidump.log
2) append
I'm inclined to say we are facing different problems on this case. With
the HP Proliant scenario I would like to recommend the following kernel
boot parameters (/etc/default/grub):
intel_idle.max_cstate=0 nox2apic intremap=off
It looks like these servers don't support x2apic and/or IRQ
POSSIBLE ONLINE WORKAROUND:
Please observe the C-states from your CPUs using powertop .
# apt-get install powertop
# powertop
tabtab
After observing that they might be oscilating between C-states (C0/C1E/C3/C6)...
please do execute the following script:
(save this script as keepcstates.sh)
From Intel Manual:
No additional power reduction actions are taken in the package C1 state.
However, if
the C1E substate is enabled, the processor automatically transitions to the
lowest
supported core clock frequency, followed by a reduction in voltage. Autonomous
power
reduction actions
With some of the core dumps I have from similar situations:
crash bt
PID: 0 TASK: 81c14440 CPU: 0 COMMAND: swapper/0
#0 [880fffa07c40] machine_kexec at 8104b391
#1 [880fffa07cb0] crash_kexec at 810d5fb8
#2 [880fffa07d80] panic at 81730335
#3
** Tags added: cts kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI occurred, please see the Integrated
Management Log for
I'd like to, please, ask anyone who things is suffering from the same
bug to check if using Proliant Servers. If not, could you please open
another bug so we can concentrate efforts on this particular bug (HP
Proliang DL360/380 + NMI) ? I recommend you to open another bug, enable
kdump (small
Any solution in sight? Otherwise I'd have to change distro and I don't
want to.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI
Setting the noautogroup option at boot time normally solves the issue.
Doesn't it work for you?
P.S. The autogroup feature is pretty useless on a server, so it's safe
to disable it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Have the same error on a HP Proliant G6 ML330 with Intel® Xeon(R) CPU
E5504 @ 2.00GHz × 4 and 10GB RAM. I also have 2 new 1TB, WD1002F9YZ in
it and configured a software RAID with Partions for SWAP (10GB), System
(100GB, ext4) und DATA (890GB, ext4)
--
You received this bug notification because
If any additional information needed please feel free to ask me about
it!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI occurred,
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI
@Michael -- if 3.7.0 is ok, and 3.8.0 is not the next logical step is to
try out the v3.8-rcN candidates out and see which of those introduced
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Shouldn't be faster to git bisect the two releases?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not syncing: An NMI occurred, please see the Integrated
I've just tested the rc1 http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.8-rc1-raring/ and it's also crashing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel
We started running into this issue on Hewlett-Packard ProLiant DL380 G6,
BIOS P62 after moving to Ubuntu 14.04 Server edition from Ubuntu 13.04
Server
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This may have been introduced by this fix as it is seen only on HP
Servers:
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/CHANGES
--
You received this bug notification because you are a member of Kernel
For me this issue occurs also with Intel + Gigabyte Mainboard, so I
can't confirm it's HP related only.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
Kernel Panic - not
Another update on this to track down the problem further:
I've tested several kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline
What I did was installing every final kernel so I noticed the last one
working without this problem seems to be http://kernel.ubuntu.com
Tested now http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/
It's also crashing. So seems that this bug / feature :-) has been
introduced in 3.8.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've bisected the differences from Ubuntu stock kernel and pf4+ kernel
configuration and I've found that the error is triggered by tue
CONFIG_SCHED_AUTOGROUP setting. Fortunately it can be disabled at boot
time adding the noautogroup parameter to grub.
With the noautogroup the Ubuntu stock
I've also tried to recompile the kernel disabling
CONFIG_X86_PCC_CPUFREQ, but the resulting kernel is still crashing on
boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Title:
I can confirm that after installing the kernel at
ftp://big-bum.uni.cx/pf-kernel/amd64/linux-
image-3.15.0-pf4%2B_3.15.0-pf4%2B-10.00.Custom_amd64.deb
the server worked for days without problem (however it's not in
production, as I'm a bit scared of using such a kernel in production)
I think
I've tried following the guide on HP site and disabled Collaborative
Power Control option in BIOS, but the issue with the stock kernel
persists. So it isn't the root cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So this seems to be related to the BIOS/OS CPU powerstate control.
Specifically PPC in the BIOS appears to be the issue.
Here is a link to HP advisory as it relates to a similar VMware issue
(in actuality, its not a vmware issue):
We are also seeing this bug on our HP DL380p Gen8's. Running:
3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have an HP Proliant dl380p gen8 with 256 GB of ram. 14.04 Installation
works, but after the reboot It crashes at almost every boot attempt.
I tried reinstalling it, It started, I upgraded the system to latest
kernel available and after the reboot it doesn't boot again, nor with
the original nor
The Kernel installed in our environment is compiled using GCC 4.8.2
(check dmesg | head). Hence I don't think this is related.
We had the kernel panic again last week (see attachment). We added the
hpwdt module to blacklist, which hopefully works around this problem. We
also updated the BIOS, but
We see this or a similar issue on a DL360 G7. As visible in the stack
trace, we are using VirtualBox. However, I think this is not related
since we used the same version on a earlier Kernel. We also upgraded to
latest VirtualBox version after the last crash, however the system
crashed again since
We're not using virtualbox. What I traced back was that it always
crashes in two functions.
update_cfs_shares() + pick_next_task_fair()
I think it has to do with compiler bug (gcc 4.9.0)
Are newer Ubuntu kernels built with that broken version probably?
I installed another kernel yesterday
Btw. the kernel I'm using currently can be found at and of page http
://big-bum.uni.cx/ftp.html
linux-image-3.15.0-pf4+_3.15.0-pf4+-10.00.Custom_amd64.deb
However ftp seems to be down currently...
--
You received this bug notification because you are a member of Kernel
Packages, which is
Have two servers within 9 days which crashed because of this bug.
Both HP DL 380 Gen8 with Ubuntu 14.04 LTS and Kernel 3.13.0-24 generic.
Copied the panic from ILO's text console:
[1863292.758326] [8108ed3f] hrtimer_interrupt+0xef/0x230
[1863292.786466] [81043087]
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can you take a picture of the panic and attach it to the bug report?
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318551
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
44 matches
Mail list logo
