Re: [Xen-devel] Fwd: Debugging "Xen BUG at ... list.h" on ARM

[Thomas Leonard <talex5@xxxxxxxxx>]

On 14 April 2014 13:00, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Mon, 2014-04-14 at 10:30 +0100, Thomas Leonard wrote:
>> Sorry, you're right, I added an extra assert there. Here's a stack
>> trace with a clean build (stable-4.4 branch + debug=y):
>>
>> (XEN) Assertion 'entry->next->prev == entry' failed, line 175, file
>> /home/tal/work/cubieboard/xen/xen/include/xen/list.h
>> (XEN) Xen BUG at /home/tal/work/cubieboard/xen/xen/include/xen/list.h:175
>> (XEN) CPU1: Unexpected Trap: Undefined Instruction
>> (XEN) ----[ Xen-4.4.1-pre  arm32  debug=y  Not tainted ]----
[...]
>> (XEN) Xen call trace:
>> (XEN)    [<002414cc>] __bug+0x28/0x44 (PC)
>> (XEN)    [<002414cc>] __bug+0x28/0x44 (LR)
>> (XEN)    [<0022e32c>] set_timer+0x1d0/0x278
>> (XEN)    [<00250480>] virt_timer_save+0x88/0x90
>
>
> This presumably implies that the timer is already active, which it
> really shouldn't be while the vcpu is scheduled.
>
> The guest here is the same stuff as
> https://github.com/talex5/xen-paratest ?

Yes (the master branch, commit 22e3b9bf). It doesn't always give the
same output, even from clean boot. Here are some more samples
(attached).


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

Attachment: xen-crashes.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel