[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [BUG] -- unable to boot 4.5-unstable after commit e13b3203990706db1313ec2aadd9a30b249ee793
On 28/08/2014 22:49, Don Slutz wrote: > The key here may be the command line options: > > (XEN) Command line: placeholder dom0_mem=2G loglvl=all > guest_loglvl=all console_timestamps=1 com1=9600,8n1 console=com1 > apic_verbosity=verbose crashkernel=256M@256M no-cpuidle > > -Don Slutz Already reported, fixed by bd083922f9e78ed19ef98e7de372e5f568402ed3 in staging. ~Andrew > > On 08/28/14 17:47, Don Slutz wrote: >> dcs-xen-54:~/xen>git-bisect good >> e13b3203990706db1313ec2aadd9a30b249ee793 is the first bad commit >> commit e13b3203990706db1313ec2aadd9a30b249ee793 >> Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> >> Date: Fri Aug 22 14:32:45 2014 +0200 >> >> x86/irq: process softirqs in irq keyhandlers >> >> Large machines with lots of interrupts can trip over the Xen >> watchdog. >> >> Suggested-by: Santosh Jodh <Santosh.Jodh@xxxxxxxxxx> >> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> >> Tested-by: Santosh Jodh <Santosh.Jodh@xxxxxxxxxx> >> >> :040000 040000 d43de46a55f8ca96c6bbcb0fcc8b705d439d44c8 >> e949c76ae45ecb1a6e1d5fce9ada5b89712fbd87 M xen >> >> This patch prevents xen from booting on my hardware. >> >> Here is the tail of the serial console output: >> >> ... >> (XEN) init IO_APIC IRQs >> (XEN) IO-APIC (apicid-pin) 0-0, 0-16, 0-17, 0-18, 0-19, 0-20, 0-21, >> 0-22, 0-23 not connected. >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 >> (XEN) number of MP IRQ sources: 15. >> (XEN) number of IO-APIC #0 registers: 24. >> (XEN) testing the IO APIC....................... >> >> >> -Don Slutz > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |