Bug 1091560 - error 4 in libpthread-2.19.90.so
Summary: error 4 in libpthread-2.19.90.so
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1088903 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 22:05 UTC by Peter H. Jones
Modified: 2016-11-24 12:42 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-25 22:37:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output showing segfault messages (76.53 KB, text/plain)
2014-04-25 22:05 UTC, Peter H. Jones
no flags Details
compressed tar of crash information. There are three crashes here, each in its own directory. (2.43 MB, application/octet-stream)
2014-04-25 22:15 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2014-04-25 22:05:23 UTC
Created attachment 889915 [details]
dmesg output showing segfault messages

Description of problem:
Several packages are giving libpthread errors during boot.
dmesg | grep -n would give:
"1054:[  284.929940] accounts-daemon[909]: segfault at 10 ip 00007f195747c4a1 sp 00007fff35a906a8 error 4 in libpthread-2.19.90.so[7f1957473000+17000]
1059:[  303.368397] polkitd[1187]: segfault at 10 ip 00007f9c8d9624a1 sp 00007fff70120808 error 4 in libpthread-2.19.90.so[7f9c8d959000+17000]
1060:[  327.910827] polkitd[1422]: segfault at 10 ip 00007fcc51f804a1 sp 00007fffaedd49f8 error 4 in libpthread-2.19.90.so[7fcc51f77000+17000]
1068:[  356.455386] polkitd[1428]: segfault at 10 ip 00007f86dd44c4a1 sp 00007fffb5d9e5e8 error 4 in libpthread-2.19.90.so[7f86dd443000+17000]
1087:[  490.237206] polkitd[1615]: segfault at 10 ip 00007f1dc79ac4a1 sp 00007fffbe629f08 error 4 in libpthread-2.19.90.so[7f1dc79a3000+17000]
1107:[  516.244983] polkitd[1747]: segfault at 10 ip 00007f243703e4a1 sp 00007fffd270a208 error 4 in libpthread-2.19.90.so[7f2437035000+17000]
1111:[  541.690869] polkitd[1821]: segfault at 10 ip 00007f29595624a1 sp 00007fff49634338 error 4 in libpthread-2.19.90.so[7f2959559000+17000]
"

Version-Release number of selected component (if applicable):
See http://kojipkgs.fedoraproject.org//work/tasks/9268/6779268/livecd.log for versions used in the build

How reproducible:
Tried just once, willing to try again

Steps to Reproduce:
1. Download, burn and boot http://kojipkgs.fedoraproject.org//work/tasks/9268/6779268/Fedora-Live-KDE-x86_64-rawhide-20140425.iso .
2. Select Troubleshooting, move to Test and Boot, and use the TAB key to remove rhgb and quiet from the command line
3. Boot

Actual results:
Segfault error messages appear. The system showed one icon on the display, then the screen went dark for a litle while, then I got KDE and Kwin crash windows. As I could not enter the password to get online in wifi, I took a tar of the crash information in /var/tmp/abrt.

Expected results:
Normal boot.

Additional info:

Comment 1 Peter H. Jones 2014-04-25 22:15:22 UTC
Created attachment 889920 [details]
compressed tar of crash information. There are three crashes here, each in its own directory.

I'm assuming the KDE crashes are caused by the segfault messages. I don't know if the problem is in libgthread, or in the programs calling it: accounts-daemon, polkit, et al.

Comment 2 Peter H. Jones 2014-04-25 22:21:48 UTC
*** Bug 1088903 has been marked as a duplicate of this bug. ***

Comment 3 Carlos O'Donell 2014-04-25 22:36:56 UTC
Your attached tarball has:
* one kernel oops
* one segfault in /lib64/libQtScript.so.4 (QTJSC::JSGlobalData::storeVPtrs())
* one trace/breakpoint trap in /lib64/libglib-2.0.so.0 (g_logv)

Something is seriously wrong with your system. You should never get random trace/breakpoint traps unless the kernel is really broken, or your hardware is broken. The kernel oops has no real information though so it's hard to determine if the hardware is at fault.

All in all there isn't enough information to determine a cause right now except for "broken hardware."

If you can reproduce this please reopen the bug with more information.


Note You need to log in before you can comment on or make changes to this bug.