← Back to team overview

kernel-packages team mailing list archive

[Bug 1358920] Re: Swith kernel to vmlinuz (from vmlinux) on ppc64el

 

IIRC, there are a few other userspace spots this will "break" (due to
silly assumptions) when we switch, but that's no excuse to not switch,
so I'll make sure we hunt those down before release.

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

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

Title:
  Swith kernel to vmlinuz (from vmlinux) on ppc64el

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  May we discuss/implement switching the kernel image type/filename on
  ppc64el from vmlinu*x* to vmlinu*z* ?

  Problem:
  ------------

  In the current situation, some issues occur because of 1) or 2):

  1) the presence of /boot/vmlinu*x*  w/ no debug symbols  (vmlinux conventionally contains debug symbols)
    - systemtap's search path includes it first, and assumes it has debug symbols, and thus fail on probes involving the "kernel" identifier
    - perf had a similar issue on trusty IIRC, which required specifying /proc/kallsyms by hand (it seems automatic on utopic)
  2) the lack of /boot/vmlinu*z*
    - kdump-config (from makedumpfile): only tests for existence of /boot/vmlinu*z*

  .. and potentially others.

  I believe the limiting factors that kept us using vmlinu*x* was either 
   1) yaboot, or 
   2) lack of zImage support for 64el on kernel.

  Neither should be a problem anymore: for 1) ppc64el uses grub only,
  and for 2) 3.16 contains the zImage-support patchset.

  
  Solution Proposal:
  -------------------------

  I had success in building, booting and installing utopic w/ vmlinuz.

  Attaching the (trivial) patches for the kernel (ubuntu-utopic.git,
  master branch) and debian-installer (src pkg).

  The install w/ mini.iso finished successfully. Although it ended up
  installing vmlinux (it download linux-image from Canonical, I guess),
  it was just a matter of installing the patched linux-image package to
  get vmlinuz installed and booted successfully.

  If there's no objection/more fixes to do, I'd submit the kernel patch
  on the kernel-team mailing list, and check what's needed to get this
  back on trusty (zImage support has 16 patches IIRC).

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


References