http://bugzilla.opensuse.org/show_bug.cgi?id=1168865 http://bugzilla.opensuse.org/show_bug.cgi?id=1168865#c1 --- Comment #1 from Michel Normand --- Created attachment 835093 --> http://bugzilla.opensuse.org/attachment.cgi?id=835093&action=edit lshw_segfault_journalctl.log I am able to recreate the problem retrieving the last lshw rpms via osc getbinaries on a P8 guest with Tumbleweed. related trace from journalctl: === Apr 07 13:50:17 twppc64le2 kernel: lshw[13715]: segfault (11) at 3401000000000028 nip 119f768a0 lr 119f779fc code 3 in lshw[119f40000+d0000] Apr 07 13:50:17 twppc64le2 kernel: lshw[13715]: code: fb210028 fb410030 fba10048 fbe10058 3b20ffff 7f7cdb78 3f008000 7b390060 Apr 07 13:50:17 twppc64le2 kernel: lshw[13715]: code: f8010070 eba40008 eb440000 60420000 <ebfe0028> 7c3fe840 7fe5fb78 40810008 Apr 07 13:50:17 twppc64le2 systemd[1]: Started Process Core Dump (PID 13719/UID 0). Apr 07 13:50:17 twppc64le2 sudo[13714]: pam_unix(sudo:session): session closed for user root Apr 07 13:50:21 twppc64le2 systemd-coredump[13720]: Process 13715 (lshw) of user 0 dumped core. Stack trace of thread 13715: #0 0x0000000119f768a0 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE4findERKS5_ (lshw + 0x368a0) #1 0x0000000119f779fc _ZNSt3setINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4lessIS5_ESaIS5_EE4findERKS5_ (lshw + 0x379fc) #2 0x0000000119f78084 _Z7enabledPKc (lshw + 0x38084) #3 0x0000000119f600a0 detect_ext2 (lshw + 0x200a0) #4 0x0000000119f581c4 _Z11scan_volumeR6hwNodeR6source (lshw + 0x181c4) #5 0x0000000119f69f2c detect_gpt (lshw + 0x29f2c) #6 0x0000000119f64a74 _Z15scan_partitionsR6hwNode (lshw + 0x24a74) #7 0x0000000119f7f810 _Z9scan_diskR6hwNode (lshw + 0x3f810) #8 0x0000000119f8907c scan_sg (lshw + 0x4907c) #9 0x0000000119fc2a54 _Z9scan_scsiR6hwNode (lshw + 0x82a54) #10 0x0000000119f514fc main (lshw + 0x114fc) #11 0x00007fffacf5804c generic_start_main (libc.so.6 + 0x2804c) #12 0x00007fffacf58224 __libc_start_main (libc.so.6 + 0x28224) Apr 07 13:50:21 twppc64le2 systemd[1]: systemd-coredump@1-13719-0.service: Succeeded. === -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168865 http://bugzilla.opensuse.org/show_bug.cgi?id=1168865#c2 --- Comment #2 from Michel Normand --- I verified that w/o lto problem disappeared for ppc64le, so submitted new https://build.opensuse.org/request/show/796551 I assume that need to keep this bug open to track failure with lto ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168865 http://bugzilla.opensuse.org/show_bug.cgi?id=1168865#c4 Martin Liška changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Blocks| |1133084 Assignee|screening-team-bugs@suse.de |martin.liska@suse.com --- Comment #4 from Martin Liška --- I can take a look. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168865 http://bugzilla.opensuse.org/show_bug.cgi?id=1168865#c6 Michel Normand changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(normand@linux.vne | |t.ibm.com) | --- Comment #6 from Michel Normand --- (In reply to Martin Liška from comment #5)

Does it also happen on aarch64 as you mentioned here: https://build.opensuse.org/request/show/796551 ?

The disabling of lto did not solve the aarch64 problem tracked in https://bugzilla.opensuse.org/show_bug.cgi?id=1169668#c2 It only helped in its callstack capture. -- You are receiving this mail because: You are on the CC list for the bug.