Bug 1377567
| Summary: | Kdump captures a extremely large vmcore | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tong Li <tonli> | ||||
| Component: | kexec-tools | Assignee: | Pratyush Anand <panand> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 25 | CC: | bhe, kdump-team-bugs, ruyang, tonli | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kexec-tools-2.0.13-7.fc25 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-31 07:36:59 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1379192 | ||||||
| Attachments: |
|
||||||
Fedora 25 kernel enabled kaslr by default so kdump default config does not work, Pratyush has patches to fix it, it will be likely accepted by upstream soon. So we should fix it in F25 compose. kexec-tools-2.0.13-7.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7a0e28b12e kexec-tools-2.0.13-7.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 1202714 [details] kdump's configuration Description of problem: Kdump captures a extremely large vmcore after a crash, which is several GBs. Version-Release number of selected component (if applicable): kexec-tools-2.0.13-5.fc26.x86_64 kernel-4.8.0-0.rc6.git4.1.fc26.x86_64 How reproducible: Steps to Reproduce: 1.echo c > /proc/sysrq-trigger 2. 3. Actual results: A vmcore file of several GBs Expected results: A vmcore file whose size is under 100M Additional info: