Hide Forgot
Created attachment 537488 [details] full valgrind log output Description of problem: SSIA Version-Release number of selected component (if applicable): valgrind-3.6.0-4.el6.x86_64 How reproducible: always Steps to Reproduce: 1. run qemu-kvm in valgrind 2. 3. Actual results: process exits in few seconds with bad alignment error Expected results: Additional info: lines around the error: ==7707== by 0x34EE2077F0: start_thread (in /lib64/libpthread-2.12.so) ==7707== by 0x34EDAE570C: clone (in /lib64/libc-2.12.so) ==7707== VG_(arena_memalign)(0x388BC9D8, 2097152, 524288000) bad alignment value 2097152 (it is too small, too big, or not a power of two) valgrind: the 'impossible' happened: VG_(arena_memalign) ==7707== at 0x3802D247: report_and_quit (m_libcassert.c:210) ==7707== by 0x3802D2AE: panic (m_libcassert.c:294) ==7707== by 0x3802D308: vgPlain_core_panic_at (m_libcassert.c:299) ==7707== by 0x3802D31A: vgPlain_core_panic (m_libcassert.c:304) ==7707== by 0x3803965A: vgPlain_arena_memalign (m_mallocfree.c:1600) ==7707== by 0x38002D44: vgMemCheck_new_block (mc_malloc_wrappers.c:200) ==7707== by 0x3800303F: vgMemCheck_memalign (mc_malloc_wrappers.c:267) ==7707== by 0x380684B4: vgPlain_scheduler (scheduler.c:1410) ==7707== by 0x380913F4: run_a_thread_NORETURN (syswrap-linux.c:95)
Created attachment 537528 [details] raise alignment limit to 4 MB Based on advice my mfranc, I've created this patch that fixes the issue for me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0936.html