<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - X crash in memcpy (RX590)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111004#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - X crash in memcpy (RX590)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111004">bug 111004</a> from <a class="email" href="mailto:maxamar@mail.ru" title="maxamar@mail.ru">maxamar@mail.ru</a> <pre>> This looks like a bug in /lib/x86_64-linux-gnu/libc.so.6, executing an instruction which isn't supported by your CPU. That's really KVM by-design bug - offending instruction is SSE movups which in conjunction with GPU address space requires KVM to emulate this SSE instruction which it can't. I insist that this is Mesa's issue as standard memcpy would need to know if it runs inside KVM & if the address is in GPU space. Mesa should have it's own memcpy at least for accessing GPU memory space. > How exactly did you "replace memcpy"? In the source code replace calls to memcpy with calls to memcpy_new. > If this isn't due to an issue with your memcpy replacement, it's probably a Mesa issue or maybe a kernel one, but most certainly not an xf86-video-amdgpu one. These messages are generated by AMD amdgpu kernel module. BTW I solved my issue by changing BIOS to UEFI in KVM, however, baremetal version still doesn't work which is not good. Now my glibc memcpy choses another path without SSE instructions, I think.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>