kernel-packages team mailing list archive

[Tim Gardner <tim.gardner@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
       Status: Triaged => In Progress

** Changed in: linux (Ubuntu)
     Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi)

** Also affects: linux (Ubuntu Wily)
   Importance: High
     Assignee: Tim Gardner (timg-tpi)
       Status: In Progress

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Vivid)
       Status: New => In Progress

** Changed in: linux (Ubuntu Vivid)
     Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Wily)
       Status: In Progress => Fix Committed

-- 
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/1453892

Title:
  ISST-LTE: Ubuntu 15.04 need to manually set the bootlist when we do
  empty bootlist install with Crocodile adapters

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  ---Problem Description---
  Base on my understanding, Ubuntu 15.4 has the bootlist setup feature, and the system will set the bootlist by itself after fresh installation, so the user don't need to set the bootlist manually. However, when we do the Ubuntu installation with empty bootlist and Crocodile adapters, such as GTO 57B4, North Rim 2CD2 and Solstice 57D7, the firmware cannot find a bootable disk to boot up after fresh installation. The installation with empty bootlist and FC disk or VSCSI works fine (the lpar can automatically find the bootable disk and boot up, no need to set the bootlist). 

  Before installation:
  Version FW830.00 (SV830_033)
   SMS (c) Copyright IBM Corp. 2000,2014 All rights reserved.
  -------------------------------------------------------------------------------
   Current Boot Sequence
   1.    None
   2.    None
   3.    None
   4.    None
   5.    None

  After installation:

  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

   No OS image was detected by firmware.
   At least one disk in the bootlist was not found yet.
   Firmware is now retrying the entries in the bootlist.
   Press ctrl-C to stop retrying.

   
  ---uname output---
  Linux conelp2 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:12:49 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
    
  Machine Type = 8408-E8E 
   
   
  ---Steps to Reproduce---
  1.Install Ubuntu 15.04
  2.Use PCIe2 4-port 1GbE Adapter
          ( loc=U78C7.001.RCH0042-P1-C8-T2 )
  and use kte (10.33.11.31) as server
  3.Enter mirror manually 
  *Server: 10.33.11.31 
  *Directory: Use default 
  *Proxy: http://10.33.11.31:3128
  4.Select disk sda/sdb
  5.After installation, let the lpar boot up by itself, and you will see the "No OS image was detected by firmware" message
   
  I do not know the specifics of the installers for the different distros, however, the
  expectation is that the installation does modify the boot list to add the newly installed device.  

  In the scenario where a valid boot list exists prior to the install,
  if the installer does not modify the boot list to prepend the newly
  installed device, it will not be discovered "automatically."  It would
  require going to the SMS menu to find the device and add it to the
  boot list.

  In the scenario where the boot list is empty, on reboot PFW will
  attempt to construct a default boot list by scanning all of the
  available devices.  We should be able to find the installed device.

  Excellent, thanks!  I knew it would rescan on an empty list but I
  wasn't sure about the rest.

  So I guess the expectation is the installer should set the boot
  device.  If this is not happening, can we get a reproduce starting
  from a empty boot list, and collect the install logs?  I will look at
  the logs to see if I can find where it is failing and will mirror to
  Ubuntu.

  At the very end of install you should be able to "go back" to the main
  menu, then select "Save debug logs", you will then see a message, "A
  simple web server has been started on this computer to serve log
  files".  Retrieve the files and attach to the bug:

  $ wget http://<node>/hardware-summary
  $ wget http://<node>/syslog

  I have reinstalled the lpar and collect logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1453892/+subscriptions