** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC MAAS ephemeral image
To manage
I will not change the status of this bug because I can not reliably rule out
that the initial issue still exists. That was reported to happen not all the
times and from the stack trace involved some locking issue in the pci scsi
adapter's driver.
Since comment #9, however, the reported stack
I've dropped the maas-images task as that is being addressed under bug
1508565
** No longer affects: maas-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM
We ran into this while setting up an OpenStack cloud using IBM POWER8
machines[1]. Unfortunately, hwe-v for Trusty isn't available
(LP:1504066) but hwe-u does indeed fix the "Oops: Exception in kernel
mode, sig: 4 [#47]" boot loop we ran into.
Since it's been advised here, and in several other
** Changed in: maas-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC MAAS ephemeral image
To manage notifications
Per Mike's testing, this is now resolved by pushing more recent images
to Releases that enable hwe-u in Trusty for PPC64EL.
So from the initial bug point of view, this is fixed and could be
marked as such.
However, as this also affects everything that's NOT ppc64el, I'd suggest
leaving it open
I can confirm using after enabling the 14.10 images in MAAS, I now have
hwe-u as an option. I can also confirm that this does not in fact work
in the case of the Power 8 when commissioning:
Error: Couldn't load kernel image
Mike
On 05/13/2015 11:25 AM, Jeff Lane wrote:
Summary:
1: Need to add
I can confirm using after enabling the 14.10 images in MAAS, I now have
hwe-u as an option. I can also confirm that this does not in fact work
in the case of the Power 8 when commissioning:
Error: Couldn't load kernel image
--
You received this bug notification because you are a member of
Summary:
1: Need to add 14.10 images from Releases Stream to even see hwe-u as an option
2: even though hwe-u is an option, it is unusable for commissioning currently
(from Releaess).
3: We really need this usable in Releases, it's gating the Power 8 work.
This morning I tried working on this a
Next, I deleted all the images I had and switched over to the Daily
stream. First, I downloaded ONLY 14.04 amd64.
Once that was ready, I ensured the Arch was set to amd64/hwe-u and again
attempted commissioning.
So using the 14.04 images only from Daily, I was able to successfully
commission
you can update this the node in maas by setting:
architecture=ppc64el/hwe-u
with maas node update or in the gui.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM
Jeff,
If you mark a system in maas as 'generic/hwe-u', then you will boot
installation with the hwe-u kernel, the install will install the hwe-u kernel,
and everything is happy.
generally speaking my experience with power is you need hwe-u. hwe-t
kernels are not stable on ppc64el.
--
You
Ok... forgive my ignorance but will setting that also apply to the
commissioning and enlistment phases as well? That seems to be the most
problematic where we're only able to boot and commission about 50% of
the time or so.
--
You received this bug notification because you are a member of
It should, then for that machine be used for commissioning.
I don't know that there is a way to set the default arch/subarch for
commissioning or enlistment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added this to maas-images. From chats with Mike, I believe that the
Vivid ephemerals are stable on Power8.
I suspect that what's happening (I have not looked too deeply into this
so this is just a guess for now) that the ephemerals are built at GA
time, and after that point only the filesystem
I got this also on the latest Ubuntu 14.04 : it's looping over this
indefinetly :
[0.193973]
[0.194023] Oops: Exception in kernel mode, sig: 4 [#3]
[0.194128] SMP NR_CPUS=2048 NUMA PowerNV
[0.194225] Modules linked in:
[0.194316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D
Using the hwe-u kernel which I think is 3.16.0-31-generic seems to have
resolved the kernel panicing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC MAAS ephemeral image
To manage notifications
Comparing the commission logs from the old kernel and current kernel it
seems the new kernel is hitting a different issue now
The 3.13.0-46 kernel is getting a panic with an NIP of:
power7_enter_nap_mode
The 3.13.0-27 kernel was dumping a trace on what looked like a H/W error:
EEH: Frozen PE#5
I have tested using the daily images for MAAS 1.7.1
The kernel from this image is 3.13.0-46.77-generic
Still getting the kernel panic. See attached.
I am finding it is only during the commissioning process that causes the
kernel panics. Once we get a good boot and commission(intermittent), we
Was there a prior Trusty kernel that did not have the panic?
Also, does this also happen with newer release, such as Utopic or Vivid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
Looking at the commission.log, it appears that the h/w is reporting
something is broken and that is not handled properly. Do you happen to
know if this happens on more than one machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This looks very similar to bug 1354459 . I think we should really test
a more recent kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC MAAS
One additional note. The kernel version in the image is pretty out of
date. The current version in -updates is 3.13.0-46.77. We may want to
ask whoever maintains the images to create an image with a newer kernel
for Trusty.
--
You received this bug notification because you are a member of
Also, you say this happens intermittently. If that is the case, we may
be able to test other kernel versions if we can provision and login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425699
Title:
kernel panic on IBM Power8 PPC MAAS
Sorry, due to the nature of the bug(kernel panic) I am not able to login
to or access the ephemeral image to grab any logs.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
27 matches
Mail list logo
