From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9CA263858C27; Thu, 2 Feb 2023 02:53:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9CA263858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675306390; bh=M6PPLosTlpunoqgNTFnDQa+Np0DbcvERgE/0wT7UsQE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Kgu2rfYp6Ni46hX4KGKR4/2Jninv+UuK6YepSxblyHSLomSvg/fF/bKPx1aynrCD+ 74wxMPEAXqZ+XQe2ywsM2luxExD7jXbjkb1g2e7IgskC8NsdcZHUbkHD0jE0vBOfdP tBoTyJ7PSV3zUY/LulTD1OjmtzftarXsgnw91mSE= From: "Qi.Chen at windriver dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30062] glibc 2.36 loader has intermittent segfault error on ppc64le Date: Thu, 02 Feb 2023 02:53:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Qi.Chen at windriver dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30062 --- Comment #7 from ChenQi --- (In reply to Carlos O'Donell from comment #6) > (In reply to ChenQi from comment #5) > > I'm running it on qemuppc64. I'll create a simple script and try to > > reproduce the issue under valgrind. >=20 > Could you please expand on this? Does this mean you're running > qemu-system-ppc64 on x86_64 hardware? Or are you running qemu-kvm on POWER > hardware? Just for clarity, all the Fedora uses I quoted are running > virtualized with qemu, but on real ppc64le hardware. Yes, I'm running qemu-system-ppc64 on x86-64 hardware. The OS is Ubuntu18.0= 4. The qemu commandline is: qemu-system-ppc64 -device virtio-net-pci,netdev=3Dnet0,mac=3D52:54:00:12:35= :06 -netdev user,id=3Dnet0,hostfwd=3Dtcp:127.0.0.1:2224-:22,hostfwd=3Dtcp:127.0.0.1:232= 5-:23,tftp=3D/buildarea2/chenqi/builds/build-poky-sysvinit/tmp/deploy/image= s/qemuppc64 -object rng-random,filename=3D/dev/urandom,id=3Drng0 -device virtio-rng-pci,rng=3Drng0 -drive file=3D/buildarea2/chenqi/builds/build-poky-sysvinit/tmp/deploy/images/qemu= ppc64/core-image-minimal-qemuppc64-20230201020834.rootfs.ext4,if=3Dvirtio,f= ormat=3Draw -usb -device usb-tablet -machine pseries -cpu POWER9 -smp 2 -m 4096 -m 4096 -smp 2 -serial mon:stdio -serial null -nographic -kernel /buildarea2/chenqi/builds/build-poky-sysvinit/tmp/deploy/images/qemuppc64/v= mlinux -append root=3D/dev/vda rw mem=3D4096M ip=3Ddhcp console=3Dhvc0 console=3D= hvc0 nohugevmalloc --=20 You are receiving this mail because: You are on the CC list for the bug.=