https://bugzilla.novell.com/show_bug.cgi?id=447432 Summary: makedumpfile fails after trigering kdump on opensuse 11.1 Beta5 Product: openSUSE 11.1 Version: Beta 5 Platform: PowerPC-64 OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugproxy@us.ibm.com QAContact: qa@suse.de Found By: Third Party Developer/Partner Partner ID: LTC 49991 =Comment: #0================================================= Pavan Naregundi - makedumpfile failed with following message on opensuse 11.1 beta5 after triggering kdump. ========================================= linux-8b3h:~ # echo c > /proc/sysrq-trigger SysRq : Trigger a crashdump Sending IPI to other cpus... Phyp-dump not supported on this hardware Interrupt 655362 (real) is invalid, disabling it. doing fast boot SysRq : Changing Loglevel Loglevel set to 1 Creating device nodes with udev udevd-event[176]: device node '/dev/mapper/control' already exists, link to '/dev/device-mapper' will not overwrite it blogd: can not open pty/tty pair: No such file or directory [NETWORK] using interface eth0 [NETWORK] using static config based on ip=9.124.111.211::9.124.111.1:255.255.255.0:linux-8b3h:eth0:none Ignoring mode none, using static configuration 2 logical volume(s) in volume group "system" now active 2 logical volume(s) in volume group "system" now active Waiting for device /dev/system/root to appear: ok node name not found fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/system/root /dev/system/root: recovering journal /dev/system/root: Clearing orphaned inode 795577 (uid=0, gid=0, mode=0100600, size=217016) /dev/system/root: clean, 159886/1310720 files, 1014680/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/system/root Nothing to delete in /var/crash. Saving dump using makedumpfile ------------------------------------------------------------------------------- read_vmcoreinfo_symbol: Invalid data in /tmp/vmcoreinfoodm7l7: SYMBOL(mem_section)=c000000000bb4400 makedumpfile Failed. Running makedumpfile -d 0 -c /proc/vmcore failed (1). Last command failed (1). bash-3.2# =================================== makedumpfile rpm version: makedumpfile-1.3.0-1.10 linux-8b3h:~ # cat /proc/cmdline root=/dev/system/root quiet sysrq=1 crashkernel=128M@16M uname -a output: linux-8b3h:~ # uname -a Linux linux-8b3h 2.6.27.5-2-ppc64 #1 SMP 2008-11-11 15:15:33 +0100 ppc64 ppc64 ppc64 GNU/Linux Machine: P55A CPU type: power 5 Checked for following rpm packages: yast2-kdump-2.17.10-1.4 kdump-0.6.4-2.1 kernel-kdump-2.6.27.5-2.2 kexec-tools-2.0.0-44.1 makedumpfile-1.3.0-1.10 device-mapper-1.02.27-6.1 =Comment: #1================================================= Sachin P. Sant - Pavan, please check with Linux on Power test team if they encountered same issue with SLES 11 Beta5 release ? =Comment: #2================================================= Sachin P. Sant - Ciju, could you please try the latest version of makedumpfile from sourceforge and verify if this issue can be recreated ? =Comment: #3================================================= Rodrigo Sampaio Vaz - I did not got this error on sles11-beta5, although I noticed that your crashkernel=128M@16M, I had to use crashkernel=256M@32M to make the vmcore dump work correctly on Power machines, it is described as required on power machines on another bug opened for previous versions of sles11. Regards, Rodrigo =Comment: #4================================================= Pavan Naregundi - Changed the dump file format from "compressed format" to "ELF", makedumpfile passed with crashkernel=256M@32M and gave the following error with crashkernel=128M@32M =================== Mounting root /dev/system/root Nothing to delete in /var/crash. Saving dump Failed. Error reading from /proc/vmcore Last command failed (1). ================== and continues to give error in "compressed format" of dump file. =Comment: #5================================================= Sachin P. Sant - I tried the latest makedumpfile from sourceforge and was able to recreate the error. Infact the makedumpfile package included is the latest. Ciju, can we mirror this bug to Novell ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.