F20 System Wide Change: Enable kdump on secureboot machines
Vivek Goyal
vgoyal at redhat.com
Fri Jul 12 20:12:56 UTC 2013
On Thu, Jul 11, 2013 at 04:46:42PM -0600, Stephen John Smoogen wrote:
[..]
> > Anyway, USB case is interesting. I have to admin I have never tried
> > dumping to USB disk either. But in theory it should work.
> >
> >
> I tried USB direct dump and USB ext3. kdump said it could see the USB disk
> in the logs and then nothing would get written.
Ok, I just took an laptop (lenovo T61, yes it is old) and installed F19
and tried kdump (echo c > /proc/sysrq-trigger) in following 3
configurations.
- Save to local disk (root, unencrypted).
- Save to a usb flash driver (4GB, ext4 file system)
- Save dump over ssh
All 3 worked for me.
Display does get reset but that happens very late and we don't see any
of the kernel messages. I see just dracut and kdump messages.
If USB did not work for you, you can try passing rd.debug on command line
(edit /etc/sysconfig/kdump) and also set "default shell" in
/etc/kdump.conf. So after failing to save dump, you should be put in a
shell. You can look around for usb device. Also debug outupt should
tell us where we are.
Thanks
Vivek
More information about the devel
mailing list