Re: [Xen-devel] Xen crash in cpupool_assign_cpu_locked spinlock

2016-04-09 Thread Andrew Cooper
On 09/04/16 19:33, Aaron Cornelius wrote:
> I am not really sure where bugs on the staging branch should be reported.  I
> just found this one and couldn't find anywhere that it had been reported yet.

This is the correct place.

CC'ing Dario who is the author of the recent scheduler changes in staging.

~Andrew

>
> I have a Xen/Ubuntu 14.04 VM (in virtualbox) with 2 CPUs allocated to it, when
> it boots I remove a CPU from the default pool (because it's allocated to a new
> credit schedule in the new cpuppol config file), and when I create the cpupool
> Xen crashes.
>
> I just pulled the staging branch from git://xenbits.xen.org/xen.git a few 
> hours
> ago.  I ran this with a fresh pull of master yesterday and I did not 
> experience
> this issue.
>
> Here are the commands:
> $ sudo xl cpupool-cpu-remove Pool-0 1
> $ sudo xl cpupool-create /etc/xen/newpool
> 
>
> Here is the new cpupool config file:
> $ cat /etc/xen/newpool
> name = "newpool"
> sched = "credit"
> cpus = ["1"]
>
> And here is the xen console output:
> (XEN) Xen BUG at spinlock.c:48
> (XEN) [ Xen-4.7-unstable  x86_64  debug=y  Not tainted ]
> (XEN) CPU:0
> (XEN) RIP:e008:[] spinlock.c#check_lock+0x3c/0x40
> (XEN) RFLAGS: 00010246   CONTEXT: hypervisor (d0v1)
> (XEN) rax: 0001   rbx: 83007ffe4148   rcx: 
> (XEN) rdx: 0001   rsi: 82cfb300   rdi: 83007ffe414e
> (XEN) rbp: 83007fd07c90   rsp: 83007fd07c90   r8:  830072629ed0
> (XEN) r9:  deadbeef   r10: 82d08025edc0   r11: 0286
> (XEN) r12: 830072629c60   r13: 830072629840   r14: 82d0802e4a40
> (XEN) r15: 82d08033bd40   cr0: 80050033   cr4: 000406a0
> (XEN) cr3: 4c536000   cr2: 7fc1e682bab5
> (XEN) ds:    es:    fs:    gs:    ss: e010   cs: e008
> (XEN) Xen code around  (spinlock.c#check_lock+0x3c/0x40):
> (XEN)  00 98 83 f2 01 39 d0 75 <02> 0b 5d c3 55 48 89 e5 f0 ff 05 49 4d 1b 00 
> 5d
> (XEN) Xen stack trace from rsp=83007fd07c90:
> (XEN)83007fd07ca8 82d08012fe1b 0001 83007fd07d18
> (XEN)82d08012ec04 0001 830072629ed0 830072629e70
> (XEN)0001 83007ffe6000 83007ffe4148 830072629840
> (XEN)0001 830072629840 82d0802f961c 82d080312980
> (XEN) 83007fd07d38 82d080101b77 83007fd07e48
> (XEN)0001 83007fd07d88 82d080102385 0006c0dd
> (XEN)fffe 83007fd07d80 83007fd0 880025cb82f8
> (XEN)82d0802f961c 82d080312980  83007fd07ef8
> (XEN)82d0801312e8 0001  0001
> (XEN) 83007fd07ef8 82d080184d21 83007faee0c0
> (XEN)7fc1e6eec004 83007fd07e48 82d08010acf7 07000206
> (XEN)83007ffea010 83007fd07ea8 83007fd07ea4 0006c0dd
> (XEN)83007ffb6000 0006c0dd  820040005000
> (XEN)820040005178 0003 000d0012 00010004
> (XEN)0001 0001 00e2 7fc1e59b67e8
> (XEN) 7ffc3a785990 00408000 7fc1e6ce3515
> (XEN)00da09e0 0001 0001 0001
> (XEN)00da09e0  ffc5ac7667a4 0033
> (XEN)83007ffb6000 880025cb82f8 7ffc3a785760 00305000
> (XEN)7ffc3a785760 7cff802f80c7 82d0802418a2 8100146a
> (XEN) Xen call trace:
> (XEN)[] spinlock.c#check_lock+0x3c/0x40
> (XEN)[] _spin_lock+0x11/0x52
> (XEN)[] schedule_cpu_switch+0x17f/0x24a
> (XEN)[] cpupool.c#cpupool_assign_cpu_locked+0x2b/0x113
> (XEN)[] cpupool_do_sysctl+0x1e2/0x6b4
> (XEN)[] do_sysctl+0x625/0x1088
> (XEN)[] lstar_enter+0xe2/0x13c
> (XEN)
> (XEN)
> (XEN) 
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at spinlock.c:48
> (XEN) 
>
> - Aaron Cornelius
>
> ___
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


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


[Xen-devel] Xen crash in cpupool_assign_cpu_locked spinlock

2016-04-09 Thread Aaron Cornelius
I am not really sure where bugs on the staging branch should be reported.  I
just found this one and couldn't find anywhere that it had been reported yet.

I have a Xen/Ubuntu 14.04 VM (in virtualbox) with 2 CPUs allocated to it, when
it boots I remove a CPU from the default pool (because it's allocated to a new
credit schedule in the new cpuppol config file), and when I create the cpupool
Xen crashes.

I just pulled the staging branch from git://xenbits.xen.org/xen.git a few hours
ago.  I ran this with a fresh pull of master yesterday and I did not experience
this issue.

Here are the commands:
$ sudo xl cpupool-cpu-remove Pool-0 1
$ sudo xl cpupool-create /etc/xen/newpool


Here is the new cpupool config file:
$ cat /etc/xen/newpool
name = "newpool"
sched = "credit"
cpus = ["1"]

And here is the xen console output:
(XEN) Xen BUG at spinlock.c:48
(XEN) [ Xen-4.7-unstable  x86_64  debug=y  Not tainted ]
(XEN) CPU:0
(XEN) RIP:e008:[] spinlock.c#check_lock+0x3c/0x40
(XEN) RFLAGS: 00010246   CONTEXT: hypervisor (d0v1)
(XEN) rax: 0001   rbx: 83007ffe4148   rcx: 
(XEN) rdx: 0001   rsi: 82cfb300   rdi: 83007ffe414e
(XEN) rbp: 83007fd07c90   rsp: 83007fd07c90   r8:  830072629ed0
(XEN) r9:  deadbeef   r10: 82d08025edc0   r11: 0286
(XEN) r12: 830072629c60   r13: 830072629840   r14: 82d0802e4a40
(XEN) r15: 82d08033bd40   cr0: 80050033   cr4: 000406a0
(XEN) cr3: 4c536000   cr2: 7fc1e682bab5
(XEN) ds:    es:    fs:    gs:    ss: e010   cs: e008
(XEN) Xen code around  (spinlock.c#check_lock+0x3c/0x40):
(XEN)  00 98 83 f2 01 39 d0 75 <02> 0b 5d c3 55 48 89 e5 f0 ff 05 49 4d 1b 00 5d
(XEN) Xen stack trace from rsp=83007fd07c90:
(XEN)83007fd07ca8 82d08012fe1b 0001 83007fd07d18
(XEN)82d08012ec04 0001 830072629ed0 830072629e70
(XEN)0001 83007ffe6000 83007ffe4148 830072629840
(XEN)0001 830072629840 82d0802f961c 82d080312980
(XEN) 83007fd07d38 82d080101b77 83007fd07e48
(XEN)0001 83007fd07d88 82d080102385 0006c0dd
(XEN)fffe 83007fd07d80 83007fd0 880025cb82f8
(XEN)82d0802f961c 82d080312980  83007fd07ef8
(XEN)82d0801312e8 0001  0001
(XEN) 83007fd07ef8 82d080184d21 83007faee0c0
(XEN)7fc1e6eec004 83007fd07e48 82d08010acf7 07000206
(XEN)83007ffea010 83007fd07ea8 83007fd07ea4 0006c0dd
(XEN)83007ffb6000 0006c0dd  820040005000
(XEN)820040005178 0003 000d0012 00010004
(XEN)0001 0001 00e2 7fc1e59b67e8
(XEN) 7ffc3a785990 00408000 7fc1e6ce3515
(XEN)00da09e0 0001 0001 0001
(XEN)00da09e0  ffc5ac7667a4 0033
(XEN)83007ffb6000 880025cb82f8 7ffc3a785760 00305000
(XEN)7ffc3a785760 7cff802f80c7 82d0802418a2 8100146a
(XEN) Xen call trace:
(XEN)[] spinlock.c#check_lock+0x3c/0x40
(XEN)[] _spin_lock+0x11/0x52
(XEN)[] schedule_cpu_switch+0x17f/0x24a
(XEN)[] cpupool.c#cpupool_assign_cpu_locked+0x2b/0x113
(XEN)[] cpupool_do_sysctl+0x1e2/0x6b4
(XEN)[] do_sysctl+0x625/0x1088
(XEN)[] lstar_enter+0xe2/0x13c
(XEN)
(XEN)
(XEN) 
(XEN) Panic on CPU 0:
(XEN) Xen BUG at spinlock.c:48
(XEN) 

- Aaron Cornelius

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