Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1952297 +++
+++ This bug was initially created as a clone of Bug #1944014 +++
Description of problem:
"makedumpfile --dump-dmesg" generata a vmcore-demsg that only differs from the original vmcore-demsg in white spaces,
```
diff -u vmcore-dmesg.txt vmcore-dmesg.txt.2
--- vmcore-dmesg.txt 2021-03-28 22:13:09.986000000 -0400
+++ vmcore-dmesg.txt.2 2021-03-28 22:13:39.920106131 -0400
@@ -397,9 +397,9 @@
[ 1.710742] vc vcsa: hash matches
[ 1.711938] RAS: Correctable Errors collector initialized.
[ 1.713736] Unstable clock detected, switching default tracing clock to "global"
-If you want to keep using the local clock, then add:
- "trace_clock=local"
-on the kernel command line
+ If you want to keep using the local clock, then add:
+ "trace_clock=local"
+ on the kernel command line
[ 1.750539] ata1.01: NODEV after polling detection
[ 1.750973] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[ 1.752885] ata1.00: 8388608 sectors, multi 16: LBA48
```
As a consequence, all kdumps in tests failed.
Version-Release number of selected component (if applicable):
kexec-tools-2.0.21-4.fc33.x86_64
How reproducible:
always reproducible at least on hpe-dl585g5-01.hpe2.lab.eng.bos.redhat.com
Steps to Reproduce:
1. Add crashekernel=auto to the kernel commandline
2. Install kexec-tools
3. Trigger sysrq
4. Run "makedumpfile --dump-dmesg" against generated vmcore to genereate vmcore-dmesg.txt.2
5. diff -u vmcore-dmesg.txt vmcore-dmesg.txt.2
Actual results:
The generated vmcore-dmesg.txt.2 is different from the original one in white spaces.
Expected results:
Two vmcore-dmesg.txt should be the same.
Additional info:
--- Additional comment from Coiby on 2021-04-22 10:42:43 HKT ---
This bug can be also reproduced in the system provisioned via "1minutetip fedora33".