opensuse / kdump Goto Github PK

Even with commit 8adf111, the OBS build contains NET_USER=0. Local build on an IBM POWER LPAR (jostaberry-4) produces a more credible number.

I haven't tried with osc build yet for lack of time.

Some systems do not have any LEDs that might be used to indicate kdump progress. It would be great to detect such systems and avoid the error message.

When you invoke kexec, you let it use the old kexec_load syscall. This does not allow for signature verification of loaded images. You should pass -a to kexec to use kexec_file_load instead (and fall back to kexec_load if the former is not present).

kdumptool randomly outputs value for --num-threads.
So an error like following happened.
makedumpfile --num-threads 5223023572093018873 -d 31 -l /proc/vmcore.
Reference: bsc#1047609

I am still fixing my account permissions issue. So I paste the patch here.

Author: Lance Wang <[email protected]>
Date:   Fri Jan 19 16:05:42 2018 +0800

    Fix m_threads missing initialization

diff --git a/kdumptool/savedump.cc b/kdumptool/savedump.cc
index e832bf9..810a67e 100644
--- a/kdumptool/savedump.cc
+++ b/kdumptool/savedump.cc
@@ -61,7 +61,7 @@ using std::ifstream;
 SaveDump::SaveDump()
     throw ()
     : m_dump(DEFAULT_DUMP), m_transfer(NULL), m_usedDirectSave(false),
-      m_useMakedumpfile(false), m_split(0), m_nomail(false)
+      m_useMakedumpfile(false), m_split(0), m_threads(0), m_nomail(false)
 {
     Debug::debug()->trace("SaveDump::SaveDump()");

While working on reproducible builds for openSUSE, I found that our kdump package now varies across builds, because of calibrate.conf

When trying to vary as little as possible, I still get this diff:

--- old//usr/lib/kdump/calibrate.conf   2022-01-21 00:00:00.000000000 +0000
+++ new//usr/lib/kdump/calibrate.conf   2022-01-21 00:00:00.000000000 +0000
@@ -4,21 +4,21 @@
 Compared:       0 xattrs
 Compared:       60 files
 Saved:          888 B
-Duration:       0.003309 seconds
+Duration:       0.003111 seconds
 Mode:           real
 Files:          636
 Linked:         2 files
 Compared:       0 xattrs
 Compared:       60 files
 Saved:          888 B
-Duration:       0.003395 seconds
-KERNEL_BASE=96924
+Duration:       0.003227 seconds
+KERNEL_BASE=96124
 KERNEL_INIT=22956
 INIT_CACHED=36088
 PAGESIZE=4096
 SIZEOFPAGE=64
 PERCPU=264
-USER_BASE=17592
-INIT_NET=4400
+USER_BASE=18196
+INIT_NET=4396
 INIT_CACHED_NET=11224
-USER_NET=3548
+USER_NET=0

What is the purpose of these values? Can they be dropped or fixed?

In issue #25, one run of the calibration scripts resulted in USER_NET=0 even though that specific configuration should make a difference between network and non-network boot. This is not expected (cf. commit 63b22ed). The zero indicates that dump saving may sometimes start before network setup, which looks like a missing ordering constraint.