kernel-packages team mailing list archive

[Omar Siam <simar@xxxxxxx>]

Above message is cut short so to make myself clear: This is the pronblem:
mapping kernel into physical memory
about to get started...
(XEN) d0v0 Unhandled invalid opcode fault/trap [#6, ec=0000]
(XEN) domain_crash_sync called from entry.S: fault at ffff82d08022a583 create_bounce_frame+0x12b/0x13a
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.6.0  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e033:[<ffffffff81f6102c>]
(XEN) RFLAGS: 0000000000000297   EM: 1   CONTEXT: pv guest (d0v0)
(XEN) rax: 0000000000000000   rbx: 0000000000200000   rcx: 0000000000200000
(XEN) rdx: 000000000005027e   rsi: 000000000005027f   rdi: 000000000025027f
(XEN) rbp: ffffffff81e03dc0   rsp: ffffffff81e03d78   r8:  ffffffff82007a20
(XEN) r9:  ffff8801fefbaff8   r10: 0000000000007ff0   r11: 0000000000200000
(XEN) r12: 000000000005027f   r13: 000000000005027f   r14: 000000000005027f
(XEN) r15: 0000000000200000   cr0: 0000000080050033   cr4: 00000000000406e0
(XEN) cr3: 0000000811e0a000   cr2: ffffc90001281000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff81e03d78:
(XEN)    0000000000200000 0000000000200000 ffffffff81f6102c 000000010000e030
(XEN)    0000000000010097 ffffffff81e03db0 000000000000e02b 000000000020006f
(XEN)    0000000000812006 ffffffff81e03e28 ffffffff81f613ca 0000000000200000
(XEN)    00000000008100ff ffffffffffe50210 00000008100ff001 000000000020006e
(XEN)    2047911e314edf5c ffff8800065eeff8 00003fffffe00000 ffff8800065efff8
(XEN)    0000010000000000 00003ffffffff000 ffffffff81e03e88 ffffffff81f63157
(XEN)    0000000000001000 ffff880000000000 00000001ff00f000 0000000100000000
(XEN)    ffff8800065ee000 00000001ffffe000 ffff8800065ed9e0 00000000065ee000
(XEN)    0000000000000000 0000000000000000 ffffffff81e03ef0 ffffffff81f669a6
(XEN)    ffffffff00000010 0000000000000000 0000000000000000 2047911e314edf5c
(XEN)    0000000000000000 2047911e314edf5c ffffffffffffffff 0000000000000000
(XEN)    ffffffff82001920 0000000000000000 0000000000000000 ffffffff81e03f30
(XEN)    ffffffff81f59c74 ffffffff8200e2e0 0000000000000000 ffffffff81e03f60
(XEN)    ffffffff81e03f5c 0000000000000000 0000000000000000 ffffffff81e03f40
(XEN)    ffffffff81f59339 ffffffff81e03ff8 ffffffff81f60de1 00600f2000000000
(XEN)    0000000100080800 0300000100000032 0000000000000005 0000000000000020
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.

-- 
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:
  Confirmed

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)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin    8784 F.... pulseaudio
   /dev/snd/controlC1:  vmadmin    8784 F.... pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware                            1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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