On Tue, Sep 20, 2016 at 04:24:47PM +0100, George Dunlap wrote:
> Thanks for your interest in the Xen Project! Sorry for the delay in
> responding -- somehow your mail either never made it to my personal
> inbox or I accidentally deleted it instead of filing it properly. I
> saw your question on I
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
include/linux/cpuhotplug.h
between commit:
dfc616d8b3df ("cpuidle/coupled: Convert to hotplug state machine")
68e694dcef24 ("powerpc/powermac: Convert to hotplug state machine")
da3ed6519b19 ("powerpc/mmu nohash: Co
xen_cpuhp_setup() calls mutex_lock() which, when CONFIG_DEBUG_MUTEXES
is defined, ends up calling xen_save_fl(). That routine expects
per_cpu(xen_vcpu, 0) to be already initialized.
Signed-off-by: Boris Ostrovsky
Reported-by: Sander Eikelenboom
---
Sander, please see if this fixes the problem. T
On 10/02/2016 12:57 PM, Sander Eikelenboom wrote:
> On 2016-10-02 18:53, Boris Ostrovsky wrote:
>> On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>>>
>>>>> Sure thing:
>>>>> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+
>>>>&g
On 10/02/2016 12:57 PM, Sander Eikelenboom wrote:
> On 2016-10-02 18:53, Boris Ostrovsky wrote:
>> On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>>>
>>>>> Sure thing:
>>>>> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+
>>>>&g
On 2016-10-02 18:53, Boris Ostrovsky wrote:
On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
Sure thing:
addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+
8101fdb9
/usr/src/new/linux-linus/arch/x86/xen/irq.c:34
asmlinkage __visible unsigned long xen_save_fl(void
On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>
>>> Sure thing:
>>> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+ 8101fdb9
>>> /usr/src/new/linux-linus/arch/x86/xen/irq.c:34
>>>
>>> asmlinkage __visible unsigned long xen_save_f
>>>
>>> (XEN) [2016-10-02 11:31:56.397]
>>>
>>> (XEN) [2016-10-02 11:31:56.397]
>>>
Hardware Dom0 crashed: rebooting
machine in 5 seconds.
Something in Linux at 8101fdb9 followed a NULL pointer. Can
you
see what it was with the linux debug symbols?
~Andrew
Sure thing:
addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+ 8101fdb9
/usr/src/new/linux-linus/arch/
On 02/10/2016 12:46, Sander Eikelenboom wrote:
> Hi All,
>
> Since the new merge window is emerging I took the liberty of testing a
> linux 4.8-rc8 tree with
> the Xen for-linus-4.9 branch pulled on top.
> Unfortunately this crashes dom0 early in boot under Xen.
> On bare-metal the same kernel boot
Hi All,
Since the new merge window is emerging I took the liberty of testing a
linux 4.8-rc8 tree with
the Xen for-linus-4.9 branch pulled on top.
Unfortunately this crashes dom0 early in boot under Xen.
On bare-metal the same kernel boots fine.
Under Xen a linux 4.8-rc8 kernel without the Xen
flight 101243 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101243/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen b3d54cead6459567d9786ad415149868ee7f2f5b
baseline version:
xen 1e75
flight 101242 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101242/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 11 guest-start fail in 101235 pass in 101242
test-armhf-armhf-xl-arndale 15 g
13 matches
Mail list logo
