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.
Description of problem:
Kernel panic when debugging with gdb. The under-debugging problematic program had a segfault issue
Version-Release number of selected component (if applicable):
2.6.32-118.el6.x86_64
How reproducible:
Once
Steps to Reproduce:
Don't know the exact steps, the following may help
1. Compile fsstress from ltp 20110228 version with debug info, it's the problematic program
2. load fsstress with gdb
3. run with "r -d /tmp -p 1 -n 100
Actual results:
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-118.el6.x86_64 #1
Call Trace:
Message from [<ffffffff814d87b9>] ? panic+0x78/0x143
syslogd@ibm-x35 [<ffffffff812fe9a6>] ? get_current_tty+0x66/0x70
50m3-02 at Mar 1 [<ffffffff8106c212>] ? do_exit+0x842/0x850
[<ffffffff810c5dff>] ? utrace_get_signal+0x4df/0x710
kernel:Kernel [<ffffffff8106c278>] ? do_group_exit+0x58/0xd0
panic - not sync [<ffffffff810816c6>] ? get_signal_to_deliver+0x1f6/0x460
ing: Attempted t [<ffffffff8100a365>] ? do_signal+0x75/0x800
o kill init!
[<ffffffff8108e09c>] ? remove_wait_queue+0x3c/0x50
[<ffffffff8106b127>] ? do_wait+0x1f7/0x250
[<ffffffff8100ab80>] ? do_notify_resume+0x90/0xc0
[<ffffffff8100b440>] ? int_signal+0x12/0x17
Expected results:
no panic
Additional info:
Comment 9RHEL Program Management
2011-04-04 02:47:45 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
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.
Comment 10RHEL Program Management
2011-10-07 15:25:51 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
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.