Re: Hpet interrupt overflow

[Andrew Cooper <andrew.cooper3@citrix.com>]

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