This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: dom0 serial input overruns

To: Ferenc Wagner <wferi@xxxxxxx>
Subject: Re: [Xen-devel] Re: dom0 serial input overruns
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 22 Mar 2011 11:27:10 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Mar 2011 08:28:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87oc54a0zc.fsf@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87zkoq6onj.fsf@xxxxxxxxxxxxx> <20110320204321.GE3948@xxxxxxxxxxxx> <87oc54a0zc.fsf@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
> 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


> 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)

Xen-devel mailing list