← Back to team overview

kernel-packages team mailing list archive

[Bug 1334793] Comment bridged from LTC Bugzilla


------- Comment From aravam@xxxxxxxxxx 2014-09-03 22:43 EDT-------
(In reply to comment #43)
> I can confirm this issue.
> I have a S814 system running PowerVM and although the install completed, I
> boot loop on the "Calling ibm,client-architecture-support..." message.
> NOTE : I installed debian powerpc for a test - and also got this message -
> and the partition rebooted - but only once - then all proceeded as expected.

Just as an FYI, I was able to workaround the issue (temporarily until we
find the fix) by using an internal version of grub (used for NIM
installs). I netbooted my LPAR that was failing as above and used the
on-disk conf file (well, copied it to my boot-server and used it as the
netboot conf file). The system rebooted once for c-a-s negotiation, and
then successfully booted to login prompt!

So, I believe the issue is in the grub shipped with Ubuntu. I did a
quick test of setting an nvram variable at the OF prompt (ibm,fw-new-
mem-def) to true, and then booting to grub, rebooting from the grub
prompt and checking the variable again. It's value was now false. The
Linux kernel negotiates this value to true, so I think that's why we end
up in a c-a-s loop. Assigning over to Paulo for now.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

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

Status in “linux” package in Ubuntu:

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@30000000
  Preparing to boot Linux version 3.13.0-24-generic (buildd@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@4000
  ibm,sp              /vdevice/IBM,sp@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@30000010/disk@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@xxxxxxxxxx: 
  -Post a private note with access information to the machine that the bug is occuring on.

  == Comment: #1 - David Heller <hellerda@xxxxxxxxxx> - 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:


  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:


  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?


To manage notifications about this bug go to: