https://bugs.kde.org/show_bug.cgi?id=387940

            Bug ID: 387940
           Summary: amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0
                    0x89 0x44  (__x86_rdrand)
           Product: valgrind
           Version: 3.14 SVN
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: vex
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

I reproduced with Valgrind HEAD:

commit 3a5c5cecbd44b2daea146eeb5109d2b96353ef6d
Author: Ivo Raisr <[email protected]>
Date:   Wed Dec 13 16:59:03 2017 +0100

    Remove compiler warning about possibly uninitialized variable.

    This happened only with quite an old gcc version.
    Anyway, this commit simplifies the situation a bit.

/proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 79
model name      : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
stepping        : 1
microcode       : 0xb000024
cpu MHz         : 2700.523
cache size      : 46080 KB
physical id     : 0
siblings        : 32
core id         : 0
cpu cores       : 16
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm
constant_tsc rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni
pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
3dnowprefetch fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx
xsaveopt
bugs            :
bogomips        : 4600.09
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

Full crash log:

==27432== Warning: noted but unhandled ioctl 0x30000001 with no size/direction
hints.
==27432==    This could cause spurious value errors to appear.
==27432==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
==27432== Warning: noted but unhandled ioctl 0x27 with no size/direction hints.
==27432==    This could cause spurious value errors to appear.
==27432==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
==27432== Warning: noted but unhandled ioctl 0x7ff with no size/direction
hints.
==27432==    This could cause spurious value errors to appear.
==27432==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
==27432== Warning: noted but unhandled ioctl 0x25 with no size/direction hints.
==27432==    This could cause spurious value errors to appear.
==27432==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
==27432== Warning: noted but unhandled ioctl 0x17 with no size/direction hints.
==27432==    This could cause spurious value errors to appear.
==27432==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
==27432== Warning: set address range perms: large range [0x1000000000,
0x4e00000000) (noaccess)
==27432== Warning: set address range perms: large range [0x200000000,
0x700000000) (noaccess)
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x44 0x24 0xC
0xF
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==27432== valgrind: Unrecognised instruction at address 0x2e48f009.
==27432==    at 0x2E48F009: std::(anonymous namespace)::__x86_rdrand()
(random.cc:69)
==27432==    by 0x2E48F0F2: std::random_device::_M_getval() (random.cc:130)
==27432==    by 0x23D7F5B9: THCRandom_init (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x23D580AB: THCudaInit (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x23594EAF: at::Context::doInitCUDA() (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x5225A98: __pthread_once_slow (pthread_once.c:116)
==27432==    by 0x103777C4: __gthread_once (gthr-default.h:699)
==27432==    by 0x103777C4: call_once<at::Context::lazyInitCUDA()::<lambda()> >
(mutex:738)
==27432==    by 0x103777C4: lazyInitCUDA (Context.h:44)
==27432==    by 0x103777C4: THCPModule_initCuda(_object*) (Module.cpp:334)
==27432==    by 0x10377DCC: THCPModule_initExtension(_object*) (Module.cpp:368)
==27432==    by 0x4F1C191: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1CDAB: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1CDAB: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1E4E8: PyEval_EvalCodeEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432== Your program just tried to execute an instruction that Valgrind
==27432== did not recognise.  There are two possible reasons for this.
==27432== 1. Your program has a bug and erroneously jumped to a non-code
==27432==    location.  If you are running Memcheck and you just saw a
==27432==    warning about a bad jump, it's probably your program's fault.
==27432== 2. The instruction is legitimate but Valgrind doesn't handle it,
==27432==    i.e. it's Valgrind's fault.  If you think this is the case or
==27432==    you are not sure, please let us know and we'll try to fix it.
==27432== Either way, Valgrind will now raise a SIGILL signal which will
==27432== probably kill your program.
==27432== 
==27432== Process terminating with default action of signal 4 (SIGILL): dumping
core
==27432==  Illegal opcode at address 0x2E48F009
==27432==    at 0x2E48F009: std::(anonymous namespace)::__x86_rdrand()
(random.cc:69)
==27432==    by 0x2E48F0F2: std::random_device::_M_getval() (random.cc:130)
==27432==    by 0x23D7F5B9: THCRandom_init (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x23D580AB: THCudaInit (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x23594EAF: at::Context::doInitCUDA() (in
/opt/conda/lib/python2.7/site-packages/torch/lib/libATen.so.1)
==27432==    by 0x5225A98: __pthread_once_slow (pthread_once.c:116)
==27432==    by 0x103777C4: __gthread_once (gthr-default.h:699)
==27432==    by 0x103777C4: call_once<at::Context::lazyInitCUDA()::<lambda()> >
(mutex:738)
==27432==    by 0x103777C4: lazyInitCUDA (Context.h:44)
==27432==    by 0x103777C4: THCPModule_initCuda(_object*) (Module.cpp:334)
==27432==    by 0x10377DCC: THCPModule_initExtension(_object*) (Module.cpp:368)
==27432==    by 0x4F1C191: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1CDAB: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1CDAB: PyEval_EvalFrameEx (in
/opt/conda/lib/libpython2.7.so.1.0)
==27432==    by 0x4F1E4E8: PyEval_EvalCodeEx (in
/opt/conda/lib/libpython2.7.so.1.0)

Let me know if you need more information.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to