Bug 1088903 - segfaults when booting
Summary: segfaults when booting
Keywords:
Status: CLOSED DUPLICATE of bug 1091560
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-17 11:59 UTC by Peter H. Jones
Modified: 2014-04-25 22:21 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-25 12:47:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (60.81 KB, text/plain)
2014-04-17 12:02 UTC, Peter H. Jones
no flags Details
dmesg output (64.24 KB, text/plain)
2014-04-25 02:46 UTC, Peter H. Jones
no flags Details
/var/log/messages (190.03 KB, text/plain)
2014-04-25 02:48 UTC, Peter H. Jones
no flags Details
dmesg output (61.81 KB, text/plain)
2014-04-25 04:29 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2014-04-17 11:59:14 UTC
Description of problem:
segfault errors while booting

Version-Release number of selected component (if applicable):
3.15.0-0.rc1.git1.1.fc21.x86_64

How reproducible:
Every time

Steps to Reproduce:

1. Download and boot http://kojipkgs.fedoraproject.org//work/tasks/6983/6746983/Fedora-Live-KDE-x86_64-rawhide-20140416.iso

Actual results:
segfault errors in dmesg output:
"911:[  275.319694] accounts-daemon[669]: segfault at 10 ip 00007fb09df8e4a1 sp 00007fff3faa2e08 error 4 in libpthread-2.19.90.so[7fb09df85000+17000]
917:[  290.351943] polkitd[1027]: segfault at 10 ip 00007ff322d9f4a1 sp 00007fff1e45f708 error 4 in libpthread-2.19.90.so[7ff322d96000+17000]
918:[  314.772255] polkitd[1245]: segfault at 10 ip 00007f7a0d7fe4a1 sp 00007fff3c63a718 error 4 in libpthread-2.19.90.so[7f7a0d7f5000+17000]
923:[  341.230225] polkitd[1251]: segfault at 10 ip 00007f2d26bf14a1 sp 00007fff44e6ab38 error 4 in libpthread-2.19.90.so[7f2d26be8000+17000]
926:[  366.290405] polkitd[1254]: segfault at 10 ip 00007f4e20e914a1 sp 00007fff2c225168 error 4 in libpthread-2.19.90.so[7f4e20e88000+17000]"

Expected results:
No errors

Additional info:
Package version information available at http://kojipkgs.fedoraproject.org//work/tasks/6983/6746983/livecd.log .

When I let the system run for a few minutes, I found indications of abrt dumps in /var/log/messages. Could collect these if needed..

Comment 1 Peter H. Jones 2014-04-17 12:02:22 UTC
Created attachment 887161 [details]
dmesg output

Comment 2 Josh Boyer 2014-04-17 12:31:28 UTC
There's nothing here that indicates a kernel issue.  Those are segfaults in userspace.  If you're going to test rawhide live images, please take a few moments and try and narrow down which area is having issues before reporting your bugs.

If you have some information that would indicate it's a kernel issue, attach that and reopen.

Comment 3 Peter H. Jones 2014-04-25 02:46:33 UTC
Created attachment 889514 [details]
dmesg output

I think the problem is in glib2-2.40.0-1.fc21.x86_64 . If I search for the segfault messages in dmesg output, I get:
"grep -n segfault dmesg.txt
949:[  257.165558] accounts-daemon[842]: segfault at 10 ip 00007fb880a1a4a1 sp 00007fff071a6448 error 4 in libpthread-2.19.90.so[7fb880a11000+17000]
964:[  273.934743] polkitd[1173]: segfault at 10 ip 00007fe8fd79c4a1 sp 00007fff61040d08 error 4 in libpthread-2.19.90.so[7fe8fd793000+17000]
965:[  298.598883] polkitd[1347]: segfault at 10 ip 00007fed852184a1 sp 00007fffae2c34b8 error 4 in libpthread-2.19.90.so[7fed8520f000+17000]
969:[  323.898170] polkitd[1350]: segfault at 10 ip 00007f3669a924a1 sp 00007ffffc96ee88 error 4 in libpthread-2.19.90.so[7f3669a89000+17000]
973:[  348.926229] polkitd[1353]: segfault at 10 ip 00007f95daf134a1 sp 00007fffb3ba69c8 error 4 in libpthread-2.19.90.so[7f95daf0a000+17000]
" , and if I rpm -qf /usr/lib/libpthread-2*, the package name is glib or so.

If I try to change the component, midori starts using the CPU at 100%.

Comment 4 Peter H. Jones 2014-04-25 02:48:07 UTC
Created attachment 889515 [details]
/var/log/messages

/var/log/messages contains several of the segfault messages.

Comment 5 Peter H. Jones 2014-04-25 02:55:57 UTC
The attachments above occurred when I booted http://kojipkgs.fedoraproject.org//work/tasks/4818/6774818/Fedora-Live-KDE-x86_64-rawhide-20140424.iso . I selected Troubleshooting, and Check Media and Boot. I used the TAB key to remove rhgb and quiet from the command line.

Networking seems to start, but attempting to sftp my files gave an unknown host error. When I plugged in a USB disk, I was surprised to see it contained errors, as I was sure I had closed it properly when it was used previously. When I ran e2fsck on another, running system, I got a number of correctable errors.

Comment 6 Peter H. Jones 2014-04-25 04:29:32 UTC
Created attachment 889525 [details]
dmesg output

This is the most succint dmesg file I have been able to produce. I produced it using the internal DVD drive of an HP G61. Attempting to test media and boot failed at about 46%. Booted without rhgb and quiet. Software versions are in http://kojipkgs.fedoraproject.org//work/tasks/4818/6774818/livecd.log :
kernel-3.15.0-0.rc2.git2.1.fc21.x86_64
glibc-2.19.90-11.fc21.x86_64

grep -n segfault dmesg.txt gives:
"911:[   75.588890] accounts-daemon[656]: segfault at 10 ip 00007f49f3b824a1 sp 00007fff77087a28 error 4 in libpthread-2.19.90.so[7f49f3b79000+17000]
934:[   94.496448] polkitd[1070]: segfault at 10 ip 00007f0d7b82a4a1 sp 00007fff2b4ca028 error 4 in libpthread-2.19.90.so[7f0d7b821000+17000]
935:[  119.131330] polkitd[1250]: segfault at 10 ip 00007fe8c8ccf4a1 sp 00007ffff81bac38 error 4 in libpthread-2.19.90.so[7fe8c8cc6000+17000]
940:[  144.402565] polkitd[1254]: segfault at 10 ip 00007fd236bf94a1 sp 00007ffff2754ed8 error 4 in libpthread-2.19.90.so[7fd236bf0000+17000]
943:[  169.488440] polkitd[1259]: segfault at 10 ip 00007ffda2e3b4a1 sp 00007fff69df2a68 error 4 in libpthread-2.19.90.so[7ffda2e32000+17000]
"

Comment 7 Josh Boyer 2014-04-25 12:47:42 UTC
My comment #2 still applies.  There's nothing that indicates a kernel problem here.  You said you believe it's a glib problem, so perhaps file a bug there.  However, it sounds like whatever you're writing the images to is starting to fail and test media is finding that.  Incomplete image writing for whatever reason may be causing your problems.

Comment 8 Peter H. Jones 2014-04-25 22:21:48 UTC

*** This bug has been marked as a duplicate of bug 1091560 ***


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