From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ferenc Wagner <wferi@niif.hu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: dom0 serial input overruns
Date: Tue, 22 Mar 2011 11:27:10 -0400 [thread overview]
Message-ID: <20110322152710.GA27284@dumpdata.com> (raw)
In-Reply-To: <87oc54a0zc.fsf@tac.ki.iif.hu>
> the boot loader). However, this lossage isn't accompanied by any
Oooh, strange.
> warning. I hope this answers your question. I also run the exact same
> hardware configuration without Xen, and the Linux console is perfectly
> solid in that case (like it should under hardware flow control). As an
OK.
> illustration, here's the serial output of querying ioapic info on the
> Xen console:
Can you do '*' in the debug console. There are some other ones that I
curious. Mainly what the IRQ 4 in your Linux dom0 maps to what vector.
Looking at your IOAPIC output:
> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> (XEN) 04 001 01 0 0 0 0 0 1 1 38
it should be going to the first CPU (CPU 0), but I am not sure about
the other flags... We had some issue with Xen 4.0 where IRQs below
16 would not be set correctly. It would only go to the first CPU
instead of being broadcast to all of them. Look for a thread from 'M A Young'
about keyboard issues.
.. If you boot just baremetal (so no Xen) and you give it 'apic=debug'
it should print the IOAPIC output. Can you see what this? I am
very curious to see if GSI 4 has similar looking flags set (the vector
value is going to be different)
next prev parent reply other threads:[~2011-03-22 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 11:02 dom0 serial input overruns Ferenc Wagner
2011-03-20 20:43 ` Konrad Rzeszutek Wilk
2011-03-21 16:32 ` Ferenc Wagner
2011-03-22 15:27 ` Konrad Rzeszutek Wilk [this message]
2011-03-22 15:48 ` Trolle Selander
2011-03-22 22:08 ` Ferenc Wagner
2011-03-23 18:57 ` Ferenc Wagner
2011-03-24 11:54 ` Konrad Rzeszutek Wilk
2011-03-24 14:07 ` Ferenc Wagner
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=20110322152710.GA27284@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=wferi@niif.hu \
--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 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.