Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Bug #1577018 reported by Omar Siam
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

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.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vmadmin 7610 F.... pulseaudio
 /dev/snd/controlC1: vmadmin 7610 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
InstallationDate: Installed on 2015-06-27 (332 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df ro dom0_mem=8G,min:8G,max:8G 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-22.40-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-24 (30 days ago)
UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev sambashare sudo tape video
_MarkForUpload: True
dmi.bios.date: 11/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd11/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Omar Siam (simar-w) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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
Revision history for this message
Omar Siam (simar-w) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Omar Siam (simar-w) wrote : CRDA.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : IwConfig.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : JournalErrors.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : Lspci.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : Lsusb.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcEnviron.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcModules.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : PulseList.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : UdevDb.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : WifiSyslog.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : Re: Kernel crashes on dom0 startup when dom0_mem is set
Download full text (11.1 KiB)

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) (<email address hidden>) (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:...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Omar Siam (simar-w) wrote :

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.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Omar Siam (simar-w) wrote :

yes, yesterdays 4.6.0-040600rc7-generic still crashes if set and boots if not.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Omar Siam (simar-w) wrote :

Changed Mainboard to some ASUS. Works for me now.

summary: - Kernel crashes on dom0 startup when dom0_mem is set
+ Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy (e.
+ g. GA-78LMT-USB3 Rev 5.0 BIOS FA)
description: updated
Revision history for this message
Omar Siam (simar-w) wrote : AlsaInfo.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : CRDA.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : IwConfig.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : JournalErrors.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : Lspci.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : Lsusb.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcEnviron.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : ProcModules.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : PulseList.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : UdevDb.txt

apport information

Revision history for this message
Omar Siam (simar-w) wrote : WifiSyslog.txt

apport information

To post a comment you must log in.