Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRed Hat Case Diagnostics
2011-06-06 07:21:22 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: /usr/sbin/prelink -av -mR -f
comment: don't know, it is an automatic cron job.
component: prelink
executable: /usr/sbin/prelink
kernel: 2.6.32-131.0.15.el6.x86_64
package: prelink-0.4.4-1.el6
reason: Process /usr/sbin/prelink was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)
reproduce: 1.it is a cron job, from the system. no idea
2.
3.
time: 1307344778
uid: 0
backtrace: [New Thread 5856]
Core was generated by `/usr/sbin/prelink -av -mR -f'.
Program terminated with signal 6, Aborted.
#0 0x000000000043c63b in ?? ()
Thread 1 (Thread 5856):
#0 0x000000000043c63b in ?? ()
No symbol table info available.
#1 0x0000000000455995 in ?? ()
No symbol table info available.
#2 0x0000000000402003 in ?? ()
No symbol table info available.
#3 0x000000000040f232 in ?? ()
No symbol table info available.
#4 0x000000000044e6cb in ?? ()
No symbol table info available.
#5 0x0000000000400349 in ?? ()
No symbol table info available.
#6 0x00007fffa0834f98 in ?? ()
No symbol table info available.
#7 0x0000000000000000 in ?? ()
No symbol table info available.
No shared libraries loaded at this time.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
rax 0x0 0
rbx 0x7fffa07c95f0 140735885907440
rcx 0xffffffffffffffff -1
rdx 0x6 6
rsi 0x16e0 5856
rdi 0x16e0 5856
rbp 0x7fffa0834de0 0x7fffa0834de0
rsp 0x7fffa07c94b8 0x7fffa07c94b8
r8 0x8 8
r9 0xffffffff 4294967295
r10 0x8 8
r11 0x202 514
r12 0x63ce5 408805
r13 0x7fffa0834d60 140735886347616
r14 0x7fffa07eeff8 140735886061560
r15 0xe29 3625
rip 0x43c63b 0x43c63b
eflags 0x202 [ IF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
No function contains program counter for selected frame.
Comment 2Red Hat Case Diagnostics
2011-06-06 07:21:57 UTC
Comment 8RHEL Program Management
2011-07-06 01:14:37 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.