Carlos E. R. wrote:
On Thursday, 2008-11-27 at 18:49 +0200, Dave Plater wrote:
I think that kdump is what you want, it doesn't work with suspend but it should work in your case. There's a wiki entry on it as well, it works with kexec to load a new kernel when the running one crashes. If that fails you'll need to use a debug kernel and kdb.
I don't understand.
I have read the article, if it is http://en.opensuse.org/Kdump
It says:
1. Add the crashkernel=size@offset option to your bootloader configuration. See the table below for recommended options for the different architectures. Then reboot. 2. Load the panic kernel with kexec -p vmlinuz --append="command_line" --initrd="initrd". The command line should include the root file system (root=), the irqpoll and reset_devices options and should end with the runlevel you would like to have in the kdump environment (preferably 1). 3. Now crash the kernel, for testing you can use Sysrq-c. 4. In the kdump environment, copy /proc/vmcore away. 5. Reboot.
yast2-kdump module sets everything up.
Step 1.
Where exactly do I add the "crashkernel=64M@16M" option? Here, inside the kernel line?
AFAIK it's the memory space reserved for the panic kernel.
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.1 Beta 5.2 - 2.6.27.7-3 root (hd0,7) kernel /vmlinuz-2.6.27.7-3-pae root=/dev/disk/by-label/160_test resume=/dev/disk/by-label/320_swap splash=silent showopts vga=0x317 initrd /initrd-2.6.27.7-3-pae
Step 2.
Does it means that I have to manually boot the panic kernel? In a text console, or how? What exact command do I have to type? Where?
I don't understand that paragraph, to me is like reading chinese.
yast kdump sets everything up.
Step 4.
When the kernel freezes, ¿how do I go to the kdump environment? The kernel is frozen, nothing works. No keyboard. How do I go to that kernel? What commands do I have available? How do I "copy /proc/vmcore away"? To where? The system is frozen. That kernel only has 64mb, I assume I will not have a "dd" command, I suppose.
In the yast module, you can set the path for the dump. Using the yast module helps a bit to understand kdump's mechanisms.
I'm sorry, all that kdump thing looks very nice, but is only usable by people that already know how to make use of it or are kernel devs. I don't know how to use all that. I just want to provide the bugzilla kernel people the information they request, I'm not a dev. And they don't help at all :-(
As it is, I'll have to wait till some big somebody has a problem and steps in. Meanwhile, I'l have to wait till 11.2.
-- Cheers, Carlos E. R.
There is a Yast module to set it up and it's supposed to trigger on an oops. There is also an alt/sysrq/c keyboard short cut to activate it. What I would do first with a problem such as your's is downgrade to a previous kernel, reboot, save boot.msg and confirm that it is a kernel bug. I tried to get a crash dump with an oops I was getting when starting suspend but the problem went away when kdump was activated so I haven't actually seen it in action but it's simple to install and setup with yast. Just out of interest, what is the last line in /var/log/messages at the time your system freezes? Regards Dave p -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org