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.
Bug 623446 - [abrt] NetworkManager-1:0.8.1-3.el6: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
Summary: [abrt] NetworkManager-1:0.8.1-3.el6: Process /usr/sbin/NetworkManager was kil...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard: abrt_hash:c68031c9db15e7514df7ddd5051...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 19:49 UTC by Zack Cerza
Modified: 2010-08-12 00:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-12 00:29:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.88 KB, text/plain)
2010-08-11 19:49 UTC, Zack Cerza
no flags Details

Description Zack Cerza 2010-08-11 19:49:02 UTC
abrt version: 1.1.12
architecture: x86_64
cmdline: NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
component: NetworkManager
executable: /usr/sbin/NetworkManager
kernel: 2.6.32-52.el6.x86_64
package: NetworkManager-1:0.8.1-3.el6
rating: 0
reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
time: 1280250020
uid: 0

backtrace
-----
warning: exec file is newer than core file.
[New Thread 23436]
Cannot access memory at address 0x3049a1fe88
Cannot access memory at address 0x3049a1fe88
Cannot access memory at address 0x3049a1fe88
Cannot access memory at address 0x3049a1fe88
Cannot access memory at address 0x3049a1fe88
Core was generated by `NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid'.
Program terminated with signal 11, Segmentation fault.
#0  0x000000303e275855 in ?? ()

Thread 1 (Thread 23436):
#0  0x000000303e275855 in ?? ()
No symbol table info available.
#1  0x0000000023502020 in ?? ()
No symbol table info available.
#2  0x000000004c4f0110 in ?? ()
No symbol table info available.
#3  0x0000000023502020 in ?? ()
No symbol table info available.
#4  0x0000000000000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x3049a1fe88
From                To                  Syms Read   Shared Object Library
0x000000303da00af0  0x000000303da18934  Yes         /lib64/ld-linux-x86-64.so.2
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
rax            0x303e57ae80	207204363904
rbx            0x303e57aed8	207204363992
rcx            0x303e57ae90	207204363920
rdx            0x1980490	26739856
rsi            0xa1	161
rdi            0x303e57ae80	207204363904
rbp            0x1980490	0x1980490
rsp            0x7fff19bc5bd0	0x7fff19bc5bd0
r8             0x303e57aed0	207204363984
r9             0x0	0
r10            0x2000	8192
r11            0xb	11
r12            0x303fefb368	207231103848
r13            0x30	48
r14            0x303e57aed8	207204363992
r15            0x1980490	26739856
rip            0x303e275855	0x303e275855
eflags         0x10206	[ PF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
No function contains program counter for selected frame.

How to reproduce
-----
1. 
2. 
3.

Comment 1 Zack Cerza 2010-08-11 19:49:03 UTC
Created attachment 438276 [details]
File: backtrace

Comment 2 Zack Cerza 2010-08-11 19:50:31 UTC
Sorry if this is useless; I just noticed that abrt found this crash a while back.

Comment 4 RHEL Program Management 2010-08-11 20:18:42 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 5 Dan Williams 2010-08-12 00:29:44 UTC
yeah, need more debuginfo installed...


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