* cannot get kdump to work, kexec stops in load_segments()
@ 2018-09-20 17:52 Jürgen Herrmann
2018-09-26 9:43 ` Jürgen Herrmann
0 siblings, 1 reply; 2+ messages in thread
From: Jürgen Herrmann @ 2018-09-20 17:52 UTC (permalink / raw)
To: kexec
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: cannot get kdump to work, kexec stops in load_segments()
2018-09-20 17:52 cannot get kdump to work, kexec stops in load_segments() Jürgen Herrmann
@ 2018-09-26 9:43 ` Jürgen Herrmann
0 siblings, 0 replies; 2+ messages in thread
From: Jürgen Herrmann @ 2018-09-26 9:43 UTC (permalink / raw)
To: kexec
Am 20.9.2018 19:52, schrieb Jürgen Herrmann:
> 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
Anybody??
--
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-09-26 9:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-09-20 17:52 cannot get kdump to work, kexec stops in load_segments() Jürgen Herrmann
2018-09-26 9:43 ` Jürgen Herrmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox