https://bugzilla.novell.com/show_bug.cgi?id=673917
https://bugzilla.novell.com/show_bug.cgi?id=673917#c4
Klaus Singvogel changed:
What |Removed |Added
----------------------------------------------------------------------------
Found By|--- |Community User
--- Comment #4 from Klaus Singvogel 2011-02-23 09:09:46 UTC ---
Last night another crash occured, but there was no kdump file written.
Yesterday I enabled the kdump feature:
- Installed the necessary packages.
- added in /boot/grub/menu.lst the option "crashkernel=64M@16M", which gives:
kernel /boot/vmlinuz-2.6.34.7-0.7-default
root=/dev/disk/by-id/ata-FUJITSU[...]-part2 acpi=off noacpi
resume=/dev/disk/by-id/ata-FUJITSU[...]-part1 splash=silent showopts
crashkernel=64M@16M
- enabled the kdump service:
chkconfig boot.kdump on
- and looked through /etc/sysconfig/kdump that REBOOT option is enabled (which
already was). Anything else was kept at default values:
"diff -u /etc/sysconfig/kdump /var/adm/fillup-templates/sysconfig.kdump" shows
only an additional empty line.
- finally I rebooted machine to have of the kernel option take place.
But there wasn't any file stored in /var/crash/ when crash happens last night.
I even saw in /var/log/boot.msg that option "crashkernel" is written there, and
service kdump is started.
Finally I installed now the yast-kdump module and made sure that kdump is
enabled and kdump files are written at /var/crash. Everything looks good there
too.
Any hints how to enable this?
--
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.