Version-Release number of selected component: util-linux-2.21.2-2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: lscpu crash_function: read_topology kernel: 3.6.5-1.fc17.i686 truncated backtrace: :Thread no. 1 (1 frames) : #0 read_topology at lscpu.c:615
Created attachment 642777 [details] File: core_backtrace
Created attachment 642778 [details] File: environ
Created attachment 642779 [details] File: backtrace
Created attachment 642780 [details] File: limits
Created attachment 642781 [details] File: cgroup
Created attachment 642782 [details] File: smolt_data
Created attachment 642783 [details] File: executable
Created attachment 642784 [details] File: maps
Created attachment 642785 [details] File: dso_list
Created attachment 642786 [details] File: proc_pid_status
Created attachment 642787 [details] File: open_fds
Created attachment 642788 [details] File: var_log_messages
It would be nice to have /sys and /proc dump to reproduce the problem and test possible bugfix. Please use: wget https://raw.github.com/karelzak/util-linux/master/tests/ts/lscpu/mk-input.sh chmod +x mk-input.sh ./mk-input.sh lscpu-data-dump and add the lscpu-data-dump.tar.gz to bugzilla. Thanks!
The bug is probably fixed by upstream commit d4bfa64d44e0515c59e5274d2384dedd9f9d4cc8. Fedora package will be fixed ASAP.
util-linux-2.21.2-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/util-linux-2.21.2-3.fc17
Package util-linux-2.21.2-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing util-linux-2.21.2-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18417/util-linux-2.21.2-3.fc17 then log in and leave karma (feedback).
util-linux-2.21.2-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 906143 has been marked as a duplicate of this bug. ***
*** Bug 850907 has been marked as a duplicate of this bug. ***