From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keir Fraser <keir@xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 4 serial hangs during boot
Date: Mon, 23 Jul 2012 10:13:44 -0400 [thread overview]
Message-ID: <20120723141344.GA793@phenom.dumpdata.com> (raw)
In-Reply-To: <CC2F7731.4643E%keir@xen.org>
On Fri, Jul 20, 2012 at 08:59:29PM +0100, Keir Fraser wrote:
> On 20/07/2012 20:44, "Christopher S. Aker" <caker@theshore.net> wrote:
>
> > On 7/20/12 3:31 PM, Keir Fraser wrote:
> >> Somehow dom0 disabled the serial-line interrupt during boot. Possibly it
> >> appeared as a PnP device in some BIOS table and dom0 decided to disable it
> >> because it doesn't think it is being used. Xen would usually stop this
> >> happening via programming of the IO-APIC/XT-PIC but perhaps there is some
> >> other method of disabling it on this mainboard, which Xen doesn't catch.
> >
> > Hmm -- except dom0 hasn't even booted yet at the time the serial stops
> > working. Xen is 30-60 seconds away from booting dom0 given the RAM
> > scrub still has to happen.
>
> Then it is Xen doing something to kill the serial interrupt. ;-) I haven't
> seen anything like this reported before. Not sure what to suggest really...
> Gather debug output from interrupt-related debug keys (via the xl debug-keys
> interface) I suppose. I think that would be 'i' and 'z' keys. That plus Xen
> and dom0 boot logs... something might become apparent.
What about using the serial line without the interrupt?
Meaning com1=115200,8n1,0x3f8,0
That ought to make the code go into polling and ignore the interrupt line right?
>
> -- Keir
>
> > -Chris
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-07-23 14:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 19:34 Xen 4 occasionally hangs during boot Christopher S. Aker
2011-10-13 7:04 ` Jan Beulich
2011-10-13 10:46 ` Tim Deegan
2012-07-20 17:48 ` Xen 4 serial " Christopher S. Aker
2012-07-20 17:49 ` Andrew Cooper
2012-07-20 17:58 ` Christopher S. Aker
2012-07-20 18:05 ` Andrew Cooper
2012-07-20 19:10 ` Christopher S. Aker
2012-07-20 19:25 ` Andrew Cooper
2012-07-20 19:31 ` Keir Fraser
2012-07-20 19:44 ` Christopher S. Aker
2012-07-20 19:59 ` Keir Fraser
2012-07-23 14:13 ` Konrad Rzeszutek Wilk [this message]
2012-07-23 15:26 ` Keir Fraser
2012-07-23 20:53 ` Christopher S. Aker
2012-07-23 22:03 ` Malcolm Crossley
2012-07-23 22:45 ` Malcolm Crossley
2012-07-24 9:40 ` Andrew Cooper
2012-07-24 10:32 ` Jan Beulich
2012-07-26 13:50 ` Konrad Rzeszutek Wilk
2012-07-26 14:10 ` Jan Beulich
2012-07-26 14:36 ` Konrad Rzeszutek Wilk
2012-07-24 10:46 ` Jan Beulich
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=20120723141344.GA793@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).