Bug 1442600 – When nr_cpus > 1, kdump fails as system reboots after "smpboot: Booting Node 0, Processors #1"

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1442600 - When nr_cpus > 1, kdump fails as system reboots after "smpboot: Booting Node 0, Processors #1"

Summary:	When nr_cpus > 1, kdump fails as system reboots after "smpboot: Booting Node ...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	kexec-tools (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	x86_64 Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Xunlei Pang
QA Contact:	Emma Wu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1469549 1473055
	Show dependency tree / graph

Reported:	2017-04-16 04:27 EDT by Emma Wu
Modified:	2018-05-18 00:52 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	kexec-tools-2.0.14-18.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-10 10:08:47 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0807	None	None	None	2018-04-10 10:10 EDT

Groups: None (edit)

Comment 2 Baoquan He 2017-04-17 23:03:13 EDT

amd iommu is deployed on that machine, and its support for kdump has not beed provided. 

Hi Emma, when you add amd_iommu=off into cmdline of 1st kernel, does it work well?

Thanks
Baoquan

Comment 3 Baoquan He 2017-04-17 23:03:45 EDT

And, with nr_cpus=1, it works?

Comment 12 errata-xmlrpc 2018-04-10 10:08:47 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0807

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