- Original Message -
> On Thu, 2017-07-13 at 08:07 -0400, Jan Stancek wrote:
>
> (You may want to CC the patch author... Added Paul).
I did CC him using email address from patch. Maybe some list
de-duplication dropped it?
>
> > - Original Message -
> > > Hi,
> > >
> > > I'm
On Thu, 2017-07-13 at 11:46 -0300, Gustavo Romero wrote:
> Hi Jan
> Looks like that TM unavailable exception will only able to recover
> properly if it comes from problem state and since the trigger comes
> from kernel space (kvm module) it does not match
> "if (user_mode(regs))" in
On Thu, 2017-07-13 at 08:07 -0400, Jan Stancek wrote:
(You may want to CC the patch author... Added Paul).
> - Original Message -
> > Hi,
> >
> > I'm running into Oops below on IBM PowerNV system (model 8247-22L)
> > with 4.12 trees and qemu-kvm-2.9. It triggers quickly after I start
>
Hi Jan
On 13-07-2017 09:07, Jan Stancek wrote:
>> [ 181.328511] Unrecoverable TM Unavailable Exception f60 at d0001e7d9980
>> [ 181.328605] Oops: Unrecoverable TM Unavailable Exception, sig: 6 [#1]
>> [ 181.328613] SMP NR_CPUS=2048
>> [ 181.328613] NUMA
>> [ 181.328618] PowerNV
>> [
- Original Message -
> Hi,
>
> I'm running into Oops below on IBM PowerNV system (model 8247-22L)
> with 4.12 trees and qemu-kvm-2.9. It triggers quickly after I start
> KVM guest installation:
>
> virt-install --name ppc64le_kvm_1cpu --mac 52:56:00:00:00:06 --location
> nfs://XXX
Hi,
I'm running into Oops below on IBM PowerNV system (model 8247-22L)
with 4.12 trees and qemu-kvm-2.9. It triggers quickly after I start
KVM guest installation:
virt-install --name ppc64le_kvm_1cpu --mac 52:56:00:00:00:06 --location
nfs://XXX --ram=1024 --vcpus=1 --file-size=20 --hvm
