From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: cpuidle and un-eoid interrupts at the local apic Date: Sat, 3 Aug 2013 00:32:29 +0100 Message-ID: <51FC418D.8020708@citrix.com> References: <51A908CA.7050604@citrix.com> <51F8CB15.1070608@digithi.de> <51F8DD40.2090207@citrix.com> <51FC37A9.9090809@digithi.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4886096645189369791==" Return-path: In-Reply-To: <51FC37A9.9090809@digithi.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Thimo E." Cc: Keir Fraser , Jan Beulich , Xen-devel List List-Id: xen-devel@lists.xenproject.org --===============4886096645189369791== Content-Type: multipart/alternative; boundary="------------070008010106030901080604" --------------070008010106030901080604 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit On 02/08/2013 23:50, Thimo E. wrote: > Hi, > > I've postet it already in the forum thread, but to keep all of you up > to date for this issue I am copying the logfile into this thread, too: > > XenServer crash again, attached you'll find the output with the > verbose messages Andrew inserted into the code. > > Best regards > Thimo So I can see that I did screw up the debugging patch a tad, but the information is still salvageable. Adjusted from my "interesting" idea of printk formatting, (XEN) **Pending EOI error (XEN) irq 29, vector 0x2e (XEN) s[0] irq 29, vec 0x2e, ready 0, ISR 1, TMR 0, IRR 0 (XEN) All LAPIC state: (XEN) [vector] ISR TMR IRR (XEN) [1f:01] 00000000 00000000 00000000 (XEN) [3f:20] 00016384 4095716568 00000000 (XEN) [5f:40] 00000000 4041382474 00000000 (XEN) [7f:60] 00000000 3967325758 00000000 (XEN) [9f:80] 00000000 2123395250 00000000 (XEN) [bf:a0] 00000000 1502837374 00000000 (XEN) [df:c0] 00000000 4270415335 00000000 (XEN) [ff:e0] 00000000 00000000 00000000 So Xen has been interrupted by an interrupt which it believes it has already seen, and is outstanding on the PendingEOI stack, waiting for Dom0 to actually deal with. The In Service Register indicates (given the hex/dec snafu) that only vector 0x2e is in service. I will update my debugging patch with some extra information tomorrow. ~Andrew --------------070008010106030901080604 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: 8bit
On 02/08/2013 23:50, Thimo E. wrote:
Hi,
I've postet it already in the forum thread, but to keep all of you up to date for this issue I am copying the logfile into this thread, too:
XenServer crash again, attached you'll find the output with the verbose messages Andrew inserted into the code.
Best regards
   Thimo

So I can see that I did screw up the debugging patch a tad, but the information is still salvageable.

Adjusted from my "interesting" idea of printk formatting,

(XEN) **Pending EOI error
(XEN)   irq 29, vector 0x2e
(XEN)   s[0] irq 29, vec 0x2e, ready 0, ISR 1, TMR 0, IRR 0
(XEN) All LAPIC state:
(XEN) [vector]      ISR      TMR      IRR
(XEN) [1f:01] 00000000 00000000 00000000
(XEN) [3f:20] 00016384 4095716568 00000000
(XEN) [5f:40] 00000000 4041382474 00000000
(XEN) [7f:60] 00000000 3967325758 00000000
(XEN) [9f:80] 00000000 2123395250 00000000
(XEN) [bf:a0] 00000000 1502837374 00000000
(XEN) [df:c0] 00000000 4270415335 00000000
(XEN) [ff:e0] 00000000 00000000 00000000

So Xen has been interrupted by an interrupt which it believes it has already seen, and is outstanding on the PendingEOI stack, waiting for Dom0 to actually deal with.

The In Service Register indicates (given the hex/dec snafu) that only vector 0x2e is in service.

I will update my debugging patch with some extra information tomorrow.

~Andrew
 --------------070008010106030901080604-- --===============4886096645189369791== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4886096645189369791==--