On 03/06/2018 01:34 AM, Martin Schwidefsky wrote:
On Mon, 5 Mar 2018 20:08:45 +0100
Christian Borntraeger wrote:
Do you happen to run with a recent host kernel that has
commit 7041d28115e91f2144f811ffe8a195c696b1e1d0
s390: scrub registers on kernel entry and KVM exit
Can you run with
On Mon, 5 Mar 2018 20:08:45 +0100
Christian Borntraeger wrote:
> Do you happen to run with a recent host kernel that has
>
> commit 7041d28115e91f2144f811ffe8a195c696b1e1d0
> s390: scrub registers on kernel entry and KVM exit
>
> Can you run with this on top
> diff --git a/arch/s390/kernel
On 03/05/2018 02:08 PM, Christian Borntraeger wrote:
Do you happen to run with a recent host kernel that has
commit 7041d28115e91f2144f811ffe8a195c696b1e1d0
s390: scrub registers on kernel entry and KVM exit
Yes.
Can you run with this on top
diff --git a/arch/s390/kernel/entry.S
Do you happen to run with a recent host kernel that has
commit 7041d28115e91f2144f811ffe8a195c696b1e1d0
s390: scrub registers on kernel entry and KVM exit
Can you run with this on top
diff --git a/arch/s390/kernel/entry.S b/arch/s390/kernel/entry.S
index 13a133a6015c..d6dc0e5e8f74 100644
On 5 March 2018 at 18:54, Christian Borntraeger wrote:
>
>
> On 03/05/2018 07:45 PM, Farhan Ali wrote:
>>0x03ff90752026 <+110>:svc175
>
> sys_rt_sigprocmask. r0 should not be changed by the system call.
>
>>0x03ff90752028 <+112>:lgr%r5,%r0
>> => 0x03ff9075202c <
On 03/05/2018 07:45 PM, Farhan Ali wrote:
>
>
> On 03/05/2018 06:03 AM, Stefan Hajnoczi wrote:
>> Please include the following gdb output:
>>
>> (gdb) disas swapcontext
>> (gdb) i r
>>
>> That way it's possible to see which instruction faulted and which
>> registers were being accessed.
>
On 03/05/2018 06:03 AM, Stefan Hajnoczi wrote:
Please include the following gdb output:
(gdb) disas swapcontext
(gdb) i r
That way it's possible to see which instruction faulted and which
registers were being accessed.
here is the disas out for swapcontext, this is on a coredump with
On Fri, Mar 02, 2018 at 10:30:57AM -0500, Farhan Ali wrote:
>
>
> On 03/02/2018 04:23 AM, Stefan Hajnoczi wrote:
> > On Thu, Mar 01, 2018 at 09:33:35AM -0500, Farhan Ali wrote:
> > > Hi,
> > >
> > > I have been noticing some segfaults for QEMU on s390x, and I have been
> > > hitting this issue q
On 03/02/2018 01:13 AM, Fam Zheng wrote:
On Thu, Mar 1, 2018 at 10:33 PM, Farhan Ali wrote:
Hi,
I have been noticing some segfaults for QEMU on s390x, and I have been
hitting this issue quite reliably (at least once in 10 runs of a test case).
The qemu version is 2.11.50, and I have systemd
On 03/02/2018 04:23 AM, Stefan Hajnoczi wrote:
On Thu, Mar 01, 2018 at 09:33:35AM -0500, Farhan Ali wrote:
Hi,
I have been noticing some segfaults for QEMU on s390x, and I have been
hitting this issue quite reliably (at least once in 10 runs of a test case).
The qemu version is 2.11.50, and I
On Thu, Mar 01, 2018 at 09:33:35AM -0500, Farhan Ali wrote:
> Hi,
>
> I have been noticing some segfaults for QEMU on s390x, and I have been
> hitting this issue quite reliably (at least once in 10 runs of a test case).
> The qemu version is 2.11.50, and I have systemd created coredumps
> when thi
On Thu, Mar 1, 2018 at 10:33 PM, Farhan Ali wrote:
> Hi,
>
> I have been noticing some segfaults for QEMU on s390x, and I have been
> hitting this issue quite reliably (at least once in 10 runs of a test case).
> The qemu version is 2.11.50, and I have systemd created coredumps
> when this happens
12 matches
Mail list logo
