On 12/6/24 15:08, Claudio Fontana wrote:
On 6/12/24 14:41, Philippe Mathieu-Daudé wrote:
On 28/7/23 18:43, Richard Henderson wrote:
On 7/28/23 09:05, Richard Henderson wrote:
It's the page containing both code and a page table entry that
concerns me. It seems like a kernel bug, though obvious
On 6/12/24 14:41, Philippe Mathieu-Daudé wrote:
> On 28/7/23 18:43, Richard Henderson wrote:
>> On 7/28/23 09:05, Richard Henderson wrote:
>>> It's the page containing both code and a page table entry that
>>> concerns me. It seems like a kernel bug, though obviously we
>>> shouldn't crash. I'm
On 28/7/23 18:43, Richard Henderson wrote:
On 7/28/23 09:05, Richard Henderson wrote:
It's the page containing both code and a page table entry that
concerns me. It seems like a kernel bug, though obviously we
shouldn't crash. I'm not sure what to do about it.
Bah. Of course it's not a ker
Hi,
On 7/21/23 11:08, Claudio Fontana wrote:
>
> Hello Cornelia, Richard,
>
> I had some strange behavior in an s390x TCG VM that I am debugging,
>
> and configured latest upstream QEMU with --enable-debug --enable-debug-tcg
>
> and I am running the qemu binary with -d unimp,guest_errors .
>
On 7/31/23 13:31, Claudio Fontana wrote:
> On 7/21/23 11:08, Claudio Fontana wrote:
>>
>> Hello Cornelia, Richard,
>>
>> I had some strange behavior in an s390x TCG VM that I am debugging,
>>
>> and configured latest upstream QEMU with --enable-debug --enable-debug-tcg
>>
>> and I am running the qe
On 7/21/23 11:08, Claudio Fontana wrote:
>
> Hello Cornelia, Richard,
>
> I had some strange behavior in an s390x TCG VM that I am debugging,
>
> and configured latest upstream QEMU with --enable-debug --enable-debug-tcg
>
> and I am running the qemu binary with -d unimp,guest_errors .
>
> I g
On 7/28/23 09:05, Richard Henderson wrote:
It's the page containing both code and a page table entry that concerns me. It seems like
a kernel bug, though obviously we shouldn't crash. I'm not sure what to do about it.
Bah. Of course it's not a kernel bug, since the store is to LowCore.
And o
On 7/28/23 06:29, Claudio Fontana wrote:
On 7/27/23 19:41, Richard Henderson wrote:
On 7/21/23 02:08, Claudio Fontana wrote:
Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
[Switching to Thread 0x753516c0 (LWP 215975)]
(gdb) bt
#0 0x7730dabc in __pthread_kill_implement
On 7/28/23 16:28, Richard Henderson wrote:
> On 7/28/23 07:23, Claudio Fontana wrote:
>>> It is a test environment for building packages, so the guest at the time of
>>> the error is running ./configure for the package swig-v4.1.1.tar.gz
>>>
>>> checking build system type... s390x-ibm-linux-gnu^M
On 7/28/23 16:40, Claudio Fontana wrote:
> On 7/28/23 16:28, Richard Henderson wrote:
>> On 7/28/23 07:23, Claudio Fontana wrote:
It is a test environment for building packages, so the guest at the time
of the error is running ./configure for the package swig-v4.1.1.tar.gz
chec
On 7/28/23 07:23, Claudio Fontana wrote:
It is a test environment for building packages, so the guest at the time of the
error is running ./configure for the package swig-v4.1.1.tar.gz
checking build system type... s390x-ibm-linux-gnu^M
checking host system type... s390x-ibm-linux-gnu^M
checkin
On 7/28/23 15:45, Claudio Fontana wrote:
> On 7/28/23 15:33, Richard Henderson wrote:
>> On 7/28/23 06:29, Claudio Fontana wrote:
>>> On 7/27/23 19:41, Richard Henderson wrote:
On 7/21/23 02:08, Claudio Fontana wrote:
> Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
> [Sw
On 7/28/23 06:29, Claudio Fontana wrote:
On 7/27/23 19:41, Richard Henderson wrote:
On 7/21/23 02:08, Claudio Fontana wrote:
Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
[Switching to Thread 0x753516c0 (LWP 215975)]
(gdb) bt
#0 0x7730dabc in __pthread_kill_implement
On 7/27/23 19:41, Richard Henderson wrote:
> On 7/21/23 02:08, Claudio Fontana wrote:
>> Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
>> [Switching to Thread 0x753516c0 (LWP 215975)]
>> (gdb) bt
>> #0 0x7730dabc in __pthread_kill_implementation () at
>> /lib64/libc.so.
On 7/28/23 15:33, Richard Henderson wrote:
> On 7/28/23 06:29, Claudio Fontana wrote:
>> On 7/27/23 19:41, Richard Henderson wrote:
>>> On 7/21/23 02:08, Claudio Fontana wrote:
Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
[Switching to Thread 0x753516c0 (LWP 215975)]
>
On 7/21/23 02:08, Claudio Fontana wrote:
Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
[Switching to Thread 0x753516c0 (LWP 215975)]
(gdb) bt
#0 0x7730dabc in __pthread_kill_implementation () at /lib64/libc.so.6
#1 0x772bc266 in raise () at /lib64/libc.so.6
#2
.. adding Alex, maybe something related to multithreaded TCG?
On 7/21/23 11:08, Claudio Fontana wrote:
>
> Hello Cornelia, Richard,
>
> I had some strange behavior in an s390x TCG VM that I am debugging,
>
> and configured latest upstream QEMU with --enable-debug --enable-debug-tcg
>
> and I a
Hello Cornelia, Richard,
I had some strange behavior in an s390x TCG VM that I am debugging,
and configured latest upstream QEMU with --enable-debug --enable-debug-tcg
and I am running the qemu binary with -d unimp,guest_errors .
I get:
/usr/bin/qemu-system-s390x -nodefaults -no-reboot -nogr
18 matches
Mail list logo
