Bug 684721

Summary:	kernel panic when debugging with gdb
Product:	Red Hat Enterprise Linux 6	Reporter:	Eryu Guan <eguan>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	jan.kratochvil, onestero, phan, roland
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-25 04:15:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1359574, 1366045

Description Eryu Guan 2011-03-14 10:38:02 UTC

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 9 RHEL 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 10 RHEL 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.