[Bug 1334793] Re: PowerVM: ubuntu-14.04 stuck in ibm, client-architecture-support reboot loop

Wed May 27 19:35:21 UTC 2015

This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.2

---------------
grub2 (2.02~beta2-9ubuntu1.2) trusty-proposed; urgency=medium

  * debian/patches/install_powerpc_machtypes.patch: updated: do a better job
    at detecting machine types; so as to use the right utility when updating
    nvram for the boot-device. This also fixes adding a CHRP note on the
    chrp_ibm machines, which broke PowerVM mode. (LP: #1334793)
  * debian/patches/ppc64el-disable-vsx.patch: disable the VSX instruction,
    which is enabled by default on POWER7/8 cpu models, to avoid crashes due
    to instruction exceptions. The kernel will re-enable it when necessary.
    (LP: #1454743)
  * debian/patches/ieee1275-clear-reset.patch: clear the text attribute in
    the clear command. (LP: #1454764)

 -- Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>  Wed, 13 May 2015
12:30:05 -0400

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1334793

Title:
  PowerVM: ubuntu-14.04 stuck in ibm,client-architecture-support reboot
  loop

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released

Bug description:
  ---Problem Description---
  This bug is a follow-up of Bug#110009. The problem here is after successful installation of Ubuntu 14.04, the system fails to boot the OS. When I select installed OS "Ubuntu" from grub menu, it throws below error and falls back to GRUB menu again and again:

  ..........................................................................
  ..........................................................................
  OF stdout device is: /vdevice/vty at 30000000
  Preparing to boot Linux version 3.13.0-24-generic (buildd at fisher04) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 (Ubuntu 3.13.0-24.46-generic 3.13.9)
  Detected machine type: 0000000000000101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support...
  ibm,sp              /vdevice/IBM,sp at 4000
  \
  ibm,sp              /vdevice/IBM,sp at 4000
  \
  Elapsed time since release of system processors: 10675 mins 3 secs
  error: no suitable video mode found.

  Machine Type = IBM,8286-42A Mach serial number: 1069B3T 

  ---Steps to Reproduce---
  1) Try virtual DVD installation
  2) Boot the LPAR via cdrom
      i.e try below commands from openfirmware prompt:

      0> devalias cdrom /vdevice/v-scsi at 30000010/disk at 8300000000000000
      0> boot cdrom

  3) proceed with default installation, 100% installation completes. Boot the installed OS from hard disk and you hit this "no suitable video mode found" error and system falls back to GRUB.

  Install method: virtual DVD

  Install ISO Information: ubuntu-14.04-server-ppc64el.iso

  *Additional Instructions for backup: khusriva at in.ibm.com: 
  -Post a private note with access information to the machine that the bug is occuring on.

  == Comment: #1 - David Heller <hellerda at us.ibm.com> - 2014-06-11 15:32:48 ==
  This seems to be a pretty common problem, albeit with multiple causes.  I see that you already tried some of the workarounds in similar bug here:

  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/699802

  Still, it seems likely this is due to the video mode that grub is
  attempting to user for the splash screen.  Either that, or it's a
  video driver issue at the grub level.

  Can you please try the procedure in comment #4 here:

  http://wwww.ubuntuforums.org/showthread.php?t=1471399

  This involves booting to an alternate method, such as a live cd, and
  operating on the grub config files in the newly installed system.  If
  you are unable to, or have no success with updating the files, it
  would at least be good to collect the files and attach the information
  here, before sending this back to launchpad

  If you are successful in booting to live CD on the same system where
  the boot fails, it would be good to compare the files from live CD to
  those in the failing system.

  Also, do you mind installing with Ubuntu 14.10 alpha images?

  http://cdimage.ubuntu.com/ubuntu-server/daily/current/utopic-server-
  ppc64el.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1334793/+subscriptions