kernel-packages team mailing list archive

Thread
Date
[Bug 1577018] Re: Kernel crashes on dom0 startup when dom0_mem is set

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Omar Siam <simar@xxxxxxx>
Date: Sun, 01 May 2016 12:31:05 -0000
Reply-to: Bug 1577018 <1577018@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
I'm pretty sure that most of the information I just added already are in the archive I attached to my original report. Was to creative I think. Just in case: This report was generated _after deleting the offending kernel command line_. The nature of this bug is that a kernel later than 4.2.0 just crashes _before being able to print anything_. This is all the log I can get:
(XEN) Xen version 4.6.0 (Ubuntu 4.6.0-1ubuntu4) (stefan.bader@xxxxxxxxxxxxx) (gcc (Ubuntu 5.3.1-9ubuntu1) 5.3.1 20160216) debug=n Fri Feb 19 11:37:10 UTC 2016
(XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3
(XEN) Command line: placeholder dom0_mem=8G,min:8G,max:8G ucode=-1 loglvl=all guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 9 MBR signatures
(XEN)  Found 6 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 0000000000091c00 (usable)
(XEN)  000000000009f800 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000afdf0000 (usable)
(XEN)  00000000afdf0000 - 00000000afdf3000 (ACPI NVS)
(XEN)  00000000afdf3000 - 00000000afe00000 (ACPI data)
(XEN)  00000000afe00000 - 00000000aff00000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000082f000000 (usable)
(XEN) ACPI: RSDP 000F78E0, 0014 (r0 GBT   )
(XEN) ACPI: RSDT AFDF3000, 0040 (r1 GBT    GBTUACPI 42302E31 GBTU  1010101)
(XEN) ACPI: FACP AFDF3080, 0074 (r1 GBT    GBTUACPI 42302E31 GBTU  1010101)
(XEN) ACPI: DSDT AFDF3100, 683B (r1 GBT    GBTUACPI     1000 MSFT  3000000)
(XEN) ACPI: FACS AFDF0000, 0040
(XEN) ACPI: MSDM AFDF9A00, 0055 (r3 GBT    GBTUACPI 42302E31 GBTU  1010101)
(XEN) ACPI: HPET AFDF9A80, 0038 (r1 GBT    GBTUACPI 42302E31 GBTU       98)
(XEN) ACPI: MCFG AFDF9AC0, 003C (r1 GBT    GBTUACPI 42302E31 GBTU  1010101)
(XEN) ACPI: TAMG AFDF9B00, 0022 (r1 GBT    GBT   B0 5455312E BG      101)
(XEN) ACPI: APIC AFDF9940, 00BC (r1 GBT    GBTUACPI 42302E31 GBTU  1010101)
(XEN) ACPI: SSDT AFDF9BA0, 1714 (r1 AMD    POWERNOW        1 AMD         1)
(XEN) System RAM: 32237MB (33011204kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000082f000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f5ed0
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x4008
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0]
(XEN) ACPI:             wakeup_vec[afdf000c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) Processor #3 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) Processor #4 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) Processor #5 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) Processor #6 5:2 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) Processor #7 5:2 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x10b9a201 base: 0xfed00000
(XEN) ERST table was not found
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) xstate_init: using cntxt_size: 0x3c0 and states: 0x4000000000000007
(XEN) AMD Fam15h machine check reporting enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 4000.148 MHz processor.
(XEN) Initing memory sharing.
(XEN) alt table ffff82d0802bd130 -> ffff82d0802be360
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) AMD-Vi: IOMMU not found!
(XEN) I/O virtualisation disabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) microcode: CPU0 updated from revision 0x600081c to 0x600084f
(XEN) mwait-idle: does not run on family 21 model 2
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN)  - Nested Page Tables (NPT)
(XEN)  - Last Branch Record (LBR) Virtualisation
(XEN)  - Next-RIP Saved on #VMEXIT
(XEN)  - VMCB Clean Bits
(XEN)  - DecodeAssists
(XEN)  - Pause-Intercept Filter
(XEN)  - TSC Rate MSR
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) HVM: PVH mode not supported on this platform
(XEN) spurious 8259A interrupt: IRQ7.
(XEN) CPU1: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU1 updated from revision 0x600081c to 0x600084f
(XEN) CPU2: No irq handler for vector e7 (IRQ -2147483648)
(XEN) CPU3: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU3 updated from revision 0x600081c to 0x600084f
(XEN) CPU4: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU4 updated from revision 0x600081c to 0x600084f
(XEN) CPU5: No irq handler for vector e7 (IRQ -2147483648)
(XEN) CPU6: No irq handler for vector e7 (IRQ -2147483648)
(XEN) Brought up 8 CPUs
(XEN) CPU7: No irq handler for vector e7 (IRQ -2147483648)
(XEN) ACPI sleep modes: S3
(XEN) VPMU: disabled
(XEN) MCA: Use hw thresholding to adjust polling frequency
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) mtrr: your CPUs had inconsistent variable MTRR settings
(XEN) mtrr: probably your BIOS does not setup all CPUs.
(XEN) mtrr: corrected configuration.
(XEN) MTRR default type: uncachable
(XEN) MTRR fixed ranges enabled:
(XEN)   00000-9ffff write-back
(XEN)   a0000-bffff uncachable
(XEN)   c0000-c7fff write-protect
(XEN)   c8000-fffff uncachable
(XEN) MTRR variable ranges enabled:
(XEN)   0 base 000000000000 mask ffff80000000 write-back
(XEN)   1 base 000080000000 mask ffffe0000000 write-back
(XEN)   2 base 0000a0000000 mask fffff0000000 write-back
(XEN)   3 base 0000afe00000 mask ffffffe00000 uncachable
(XEN)   4 disabled
(XEN)   5 disabled
(XEN)   6 disabled
(XEN)   7 disabled
(XEN) TOM2: 00082f000000 (WB)
(XEN) Dom0 has maximum 792 PIRQs
(XEN) NX (Execute Disable) protection active
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2224000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000810000000->0000000814000000 (2071058 pages to be allocated)
(XEN)  Init. ramdisk: 000000082ca10000->000000082effd9e0
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff82224000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008001000000
(XEN)  Start info:    ffffffff82224000->ffffffff822244b4
(XEN)  Page tables:   ffffffff82225000->ffffffff8223a000
(XEN)  Boot stack:    ffffffff8223a000->ffffffff8223b000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82400000
(XEN)  ENTRY ADDRESS: ffffffff81f591f0
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) ..................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 288kB init memory.
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.


** Changed in: linux (Ubuntu)
       Status: Incomplete => 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/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
References

[Bug 1577018] [NEW] Kernel crashes on dom0 startup when dom0_mem is set
From: Omar Siam, 2016-04-30