kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1577018

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:	Ubuntu 16.04 LTS
  Release:	16.04
  linux-image-generic:
    Installiert:           4.4.0.21.22
    Installationskandidat: 4.4.0.21.22
    Versionstabelle:
   *** 4.4.0.21.22 500
          500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
          100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system (Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using dom0_mem. This is due to this FAQ entry: http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete dom0_mem parameter)

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