Bug 2015379 - vmcore dumping failed on s390x system
Summary: vmcore dumping failed on s390x system
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: rawhide
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Philipp Rudo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2021-10-19 05:28 UTC by Baoquan He
Modified: 2022-01-18 08:55 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-18 08:55:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 195058 0 None None None 2021-11-04 08:39:43 UTC
Red Hat Issue Tracker FC-311 0 None None None 2021-10-19 05:32:05 UTC

Description Baoquan He 2021-10-19 05:28:08 UTC
Description of problem:
Kdump failed on CKI with Fedora-ark kernel. Through the test console log, it's  because vmcore dumping failed. It happened when makedumpfile collecting vmcore, so it could be caused by upstream makedupfile issue or s390 upstream kernel issue.

Below is the CKI failure, beaker job can be found there. And the dmesg log can be found through the test_console.log. 

https://datawarehouse.cki-project.org/kcidb/tests/1538570

https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/2021/09/27/377809125/build_s390x_redhat:1625277119/tests/kdump_file_load/10706058_s390x_5_test_console.log  

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora Admin user for bugzilla script actions 2021-10-19 12:38:03 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 IBM Bug Proxy 2021-11-16 14:10:25 UTC
------- Comment From tstaudt.com 2021-11-16 09:01 EDT-------
Through git bisect we found that the bug was introduced by commit:
e9e7870f90e3 ("s390/dump: introduce boot data 'oldmem_data'")

A fix is targeted for 5.16.

Comment 3 Philipp Rudo 2022-01-11 09:36:40 UTC
Hi IBM,

(In reply to IBM Bug Proxy from comment #2)
> ------- Comment From tstaudt.com 2021-11-16 09:01 EDT-------
> Through git bisect we found that the bug was introduced by commit:
> e9e7870f90e3 ("s390/dump: introduce boot data 'oldmem_data'")
> 
> A fix is targeted for 5.16.

with 5.16 released, could you please provide the commit ids for the fix?

Thanks

Comment 4 IBM Bug Proxy 2022-01-11 11:10:25 UTC
------- Comment From Alexander.Egorenkov 2022-01-11 06:05 EDT-------
Upstream fix commit: https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/arch/s390/kernel/crash_dump.c?h=fixes&id=3b90954419d4c05651de9cce6d7632bcf6977678


Note You need to log in before you can comment on or make changes to this bug.