Bug 683713

Summary:	kill: cannot kill pid 887: No such process
Product:	Red Hat Enterprise Linux 6	Reporter:	Chao Ye <cye>
Component:	kexec-tools	Assignee:	Cong Wang <amwang>
Status:	CLOSED ERRATA	QA Contact:	Chao Ye <cye>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.0	CC:	czhang, phan, rkhan
Target Milestone:	rc
Target Release:	---
Hardware:	ppc64
OS:	Linux
Whiteboard:
Fixed In Version:	kexec-tools-2_0_0-169_el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-19 14:16:08 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:

Description Chao Ye 2011-03-10 05:40:15 UTC

Description of problem:
When config kdump to raw on ppc64, got these in console:
=======================================================
Free memory/Total memory (free %): 139136 / 231296 ( 60.155 )
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "vg_ibmjs2207" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "vg_ibmjs2207" now active
Free memory/Total memory (free %): 134656 / 231296 ( 58.218 )
Saving to partition /dev/sda3
Free memory/Total memory (free %): 134656 / 231296 ( 58.218 )
kill: cannot kill pid 887: No such process
Saving core complete
Restarting system.

Version-Release number of selected component (if applicable):
kernel-2.6.32-119.el6
kexec-tools-2.0.0-167.el6

How reproducible:
100%

Steps to Reproduce:
1.Install RHEL6.1-20110224.2
2.Update kernel/kexec-tools
3.Config kdump to raw(such as /dev/sda3)
  
Actual results:
Got "kill: cannot kill pid 887: No such process"

Expected results:
No such msg

Additional info:

Comment 3 Chao Ye 2011-03-18 10:02:32 UTC

Tested with latest build:
=====================================================
[root@ibm-js22-07 ~]# service kdump status
Kdump is operational
[root@ibm-js22-07 ~]# rpm -q kernel kexec-tools
kernel-2.6.32-122.el6.ppc64
kexec-tools-2.0.0-171.el6.ppc64
[root@ibm-js22-07 ~]# tail /etc/kdump.conf 
#kdump_post /var/crash/scripts/kdump-post.sh
#extra_bins /usr/bin/lftp
#disk_timeout 30
#extra_modules gfs2
#options modulename options
#default shell

raw /dev/sda3
core_collector makedumpfile -c --message-level 1 -d 31
default shell
[root@ibm-js22-07 ~]# touch /etc/kdump.conf 
[root@ibm-js22-07 ~]# service kdump restart
Stopping kdump:[  OK  ]
Detected change(s) the following file(s):

  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.32-122.el6.ppc64kdump.img
Starting kdump:[  OK  ]
[root@ibm-js22-07 ~]# echo c > /proc/sysrq-trigger
--------------------------------------------------------------------------------------
mdadm: No arrays found in config file or automatically
Free memory/Total memory (free %): 150208 / 231296 ( 64.9419 )
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "vg_ibmjs2207" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "vg_ibmjs2207" now active
Free memory/Total memory (free %): 149312 / 231296 ( 64.5545 )
Saving to partition /dev/sda3
Free memory/Total memory (free %): 149312 / 231296 ( 64.5545 )
Copying data                       : [100 %] 
Saving core complete
Restarting system.
......

No "kill: cannot kill pid 887: No such process" found.
Change status to VERIFIED.

Comment 4 errata-xmlrpc 2011-05-19 14:16:08 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0736.html