From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Hpet interrupt overflow
Date: Tue, 13 Aug 2013 10:33:33 +0100
Message-ID: <5209FD6D.5080606@citrix.com>
References: <1375735116-31466-1-git-send-email-andrew.cooper3@citrix.com>
	<5200C95F02000078000E9893@nat28.tlf.novell.com>
	<5200D0B8.4060706@citrix.com>
	<5200FDA002000078000E999E@nat28.tlf.novell.com>
	<5200F8CD.6070504@citrix.com>
	<52011D0302000078000E9AA8@nat28.tlf.novell.com>
	<5209F672.7070107@citrix.com>
	<20130813092203.GC35164@ocelot.phlegethon.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Andrew.Cooper3@citrix.com>) id 1V9Ayv-0007Le-Ln
	for xen-devel@lists.xenproject.org; Tue, 13 Aug 2013 09:33:37 +0000
In-Reply-To: <20130813092203.GC35164@ocelot.phlegethon.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Tim Deegan <tim@xen.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On 13/08/13 10:22, Tim Deegan wrote:
> Hi, 
>
> At 10:03 +0100 on 13 Aug (1376388226), Andrew Cooper wrote:
>> We had another crash, this time with a proper stack trace.  (This was
>> using an early version stack trace improvements series)
>>
>> From the stack trace (now correctly with frame pointers), we see 9 calls
>> to handle_hpet_broadcast().
> Hmmm.  I don't think this can be following frame pointers -- or if it is
> something very odd is happening here:
>
>  ffff83043f2d62a8: [<ffff82c4c0170744>] do_IRQ+0xb12/0xbc7
>  ffff83043f2d6340: [<ffff82c4c012a178>] _spin_lock_irq+0x28/0x65
>  ffff83043f2d6388: [<ffff82c4c016805f>] common_interrupt+0x5f/0x70
>
> and here:
>
>  ffff83043f2d7548: [<ffff82c4c01a24a7>] x86_emulate+0xdf60/0x11309
>  ffff83043f2d75a8: [<ffff82c4c0107774>] evtchn_set_pending+0xc0/0x18e
>  ffff83043f2d75d8: [<ffff82c4c0107900>] notify_via_xen_event_channel+0xbe/0x124
>  ffff83043f2d76c8: [<ffff82c4c01ef9b5>] ept_next_level+0xa4/0xde
>
> Tim.
>
>

Hmm yes.  I will double check the frame pointer through exception frame
logic.

~Andrew