From: Don Slutz <dslutz@verizon.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [BUG] -- unable to boot 4.5-unstable after commit e13b3203990706db1313ec2aadd9a30b249ee793
Date: Thu, 28 Aug 2014 17:49:21 -0400 [thread overview]
Message-ID: <53FFA3E1.8080509@terremark.com> (raw)
In-Reply-To: <53FFA36A.5050106@terremark.com>
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
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@citrix.com>
> 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@citrix.com>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Tested-by: Santosh Jodh <Santosh.Jodh@citrix.com>
>
> :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
next prev parent reply other threads:[~2014-08-28 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:47 [BUG] -- unable to boot 4.5-unstable after commit e13b3203990706db1313ec2aadd9a30b249ee793 Don Slutz
2014-08-28 21:49 ` Don Slutz [this message]
2014-08-28 22:03 ` Andrew Cooper
2014-08-28 22:25 ` Don Slutz
2014-08-28 22:07 ` Don Slutz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53FFA3E1.8080509@terremark.com \
--to=dslutz@verizon.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.