From: "Jürgen Herrmann" <t-5@t-5.eu>
To: kexec@lists.infradead.org
Subject: cannot get kdump to work, kexec stops in load_segments()
Date: Thu, 20 Sep 2018 19:52:31 +0200 [thread overview]
Message-ID: <73ee47d5aea541566c89ff264c2d39ed@t-5.eu> (raw)
Hello!
I am trying to debug a hang in btrfs-send: I talked to the guys on the
linux-btrfs
mailing list and they need a kdump of the state when the hang happens.
I already set up kdump:
$ kdump-config show
DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0x24000000
/vmlinuz: symbolic link to boot/vmlinuz-4.15.0-34-generic
kdump initrd:
/initrd.img: symbolic link to boot/initrd.img-4.15.0-34-generic
current state: ready to kdump
kexec command:
/sbin/kexec -p -d --command-line="BOOT_IMAGE=/vmlinuz-4.18.6
root=UUID=a914c141-72bf-448b-847f-d64ee82d8b7b ro rootflags=subvol=@
quiet splash vt.handoff=1 nr_cpus=1 systemd.unit=kdump-tools.service
irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/initrd.img /vmlinuz
Kernel version is 4.18.6 from kernel.org
CPU: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
I did a little digging in the kernel code with printk() statements and
the execution stops in arch/x86/kernel/machine_kexec_64.c in function
load_segments(). The last printk I see is before the call of
load_segments().
A screenshot of the "test-crash" can be seen here:
https://t-5.eu/owncloud/index.php/s/WCxoNuSqnKVg6J7
What else do I need to provide in terms of information?
Best regards,
Jürgen
--
Jürgen Herrmann
https://t-5.eu
ALbertstraße 2
94327 Bogen
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2018-09-20 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 17:52 Jürgen Herrmann [this message]
2018-09-26 9:43 ` cannot get kdump to work, kexec stops in load_segments() Jürgen Herrmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73ee47d5aea541566c89ff264c2d39ed@t-5.eu \
--to=t-5@t-5.eu \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox