Bug 638114

Summary: The most recent F14 updates make my system inoperable after some time
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: fweimer, jakub, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-28 10:30:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/messages none

Description Joachim Backes 2010-09-28 09:41:51 UTC
Created attachment 450133 [details]
/var/log/messages

Description of problem:

I applied the recent updates for F14 (most are coming from
updates-testing repo).

Then I rebooted: system still runs.

Then, after some time (say about 1/2 to 1 hour), getting zillions of
crash messages (in /var/log/messages), for example

Sep 28 10:25:02 eule kernel: Process 17042(abrt-hook-ccpp) has
RLIMIT_CORE set to 1
Sep 28 10:25:02 eule kernel: Aborting core
Sep 28 10:25:02 eule kernel: eu-unstrip[17043]: segfault at 962dfc ip
00945689 sp bf9ad844 error 7 in ld-2.12.90.so[942000+20000].

I tried to reboot with ctrl+alt+del: nothing happens.

Pressing reset, going into grub: system starts booting, than hangs.

My impression: the *glibc* or *glibc-common* update make my system buggy.

Restoring my system, then updating without the updates-testing repo: No
more such messages in /var/log/messages.



Version-Release number of selected component (if applicable):
glibc-2.12.90-13
glibc-common-2.12.90-13

How reproducible:
Always (after some time)

Steps to Reproduce:
1.See description
2.
3.
  
Actual results:
See description

Expected results:


Additional info:

Comment 1 Andreas Schwab 2010-09-28 10:30:24 UTC

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