[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [Fedora-xen] Dom0 crashes with 3.17.8-300+



On Thu, Jan 22, 2015 at 11:21:14AM -0500, Bill McGonigle wrote:
> Hi, all,
> 
> My desktop is f21/Xen 4.4 and the Dom0 crashes if it's 3.17.8-300 or later.  
> 3.17.7-300 is stable.  The crashing Dom0 kernels are stable as baremetal 
> kernels.
> 
> I've tried getting 3.18 from -testing and rebuilding 4.4 locally and get the 
> same thing.  
> 
> Serial output here:
>  http://fpaste.org/173093/
> 
> Looking for ideas about what could be going on and/or how to figure out what 
> is going wrong once Dom0 starts.  
> 
> (XEN) Command line: placeholder dom0_mem=12288M,max:12288M loglvl=all 
> guest_loglvl=all com1=115200,8n1 console=com1,vga
> [    0.000000] Command line: placeholder 
> root=/dev/mapper/luks-ba790367-2232-475a-ae19-82bbf7f7ccc5 ro earlyprintk=xen 
> ipv6.disable=1 selinux=0 elevator=deadline rootflags=data=journal,relatime
> 
> The last lines are:
> (XEN) PCI add device 0000:04:00.0
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

That is not good. Would it be possible to have on the Linux line:

console=hvc0 debug initcall_debug

And on the Xen line 'sync_console'.

That will make sure you see in sync where it crashes in Linux.

Thanks!
> 
> and device 4:00.0 is the USB controller, but I suspect it's what's happening 
> next that's crashing.
> 
> The baremetal boot near there is:
> 
> [    0.217464] pci 0000:04:00.0: [1b21:1142] type 00 class 0x0c0330
> [    0.217488] pci 0000:04:00.0: reg 0x10: [mem 0xf7800000-0xf7807fff 64bit]
> [    0.217611] pci 0000:04:00.0: PME# supported from D3cold
> [    0.217635] pci 0000:04:00.0: System wakeup disabled by ACPI
> [    0.219323] pci 0000:00:1c.6: PCI bridge to [bus 04]
> [    0.219395] pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
> [    0.219416] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is 
> unsupported)
> [    0.220032] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
> [    0.220266] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) 
> *0, disabled.
> [    0.220573] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
> [    0.220803] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
> [    0.221032] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 10 11 12 14 15)
> [    0.221264] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) 
> *0, disabled.
> [    0.221569] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
> [    0.221799] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
> [    0.222099] ACPI: Enabled 5 GPEs in block 00 to 3F
> [    0.222252] vgaarb: setting as boot device: PCI:0000:00:02.0
> [    0.222321] vgaarb: device added: 
> PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
> 
> but I don't know enough about Xen boot to know if that's even useful 
> information.
> 
> Thanks,
> -Bill
> 
> -- 
> Bill McGonigle, Owner   
> BFC Computing, LLC       
> http://bfccomputing.com/ 
> Telephone: +1.855.SW.LIBRE
> Email, IM, VOIP: bill@xxxxxxxxxxxxxxxx           
> VCard: http://bfccomputing.com/vcard/bill.vcf
> Social networks: bill_mcgonigle/bill.mcgonigle
> --
> xen mailing list
> xen@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/xen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.