On Wed, 7 Mar 2018 13:21:18 +0100
Thomas Huth wrote:
> On 07.03.2018 13:16, luigi burdo wrote:
> > HI,
> >
> > i had test last git with Zoltan sam emultation but at start i recive this
> >
> > ./qemu-system-ppc -M sam460ex
> > qemu-system-ppc:
> > /home/gigi/src/tags/ppc-for-2.12-20180306/inclu
On 07.03.2018 13:16, luigi burdo wrote:
> HI,
>
> i had test last git with Zoltan sam emultation but at start i recive this
>
> ./qemu-system-ppc -M sam460ex
> qemu-system-ppc:
> /home/gigi/src/tags/ppc-for-2.12-20180306/include/qemu/rcu.h:89:
> rcu_read_unlock: asserzione "p_rcu_reader->depth !=
HI,
i had test last git with Zoltan sam emultation but at start i recive this
./qemu-system-ppc -M sam460ex
qemu-system-ppc:
/home/gigi/src/tags/ppc-for-2.12-20180306/include/qemu/rcu.h:89:
rcu_read_unlock: asserzione "p_rcu_reader->depth != 0" non riuscita.
Annullato (core dump creato)
My m
On Tue, 6 Mar 2018 18:47:47 +0100
Thomas Huth wrote:
> On 06.03.2018 18:28, Mark Cave-Ayland wrote:
> > On 06/03/18 16:48, Thomas Huth wrote:
> >
> >> Something in the recent commits introduced a new way to cause unexpected
> >> aborts of QEMU:
> >>
> >> $ ppc64-softmmu/qemu-system-ppc64 -moni