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.
Description of problem:
I find kexec-tools doesn't works on hp-dl380g6-01.rhts.eng.bos.redhat.com.
......
Console: switching to colour frame buffer device 128x48
fb0: radeondrmfb frame buffer device
drm: registered panic notifier
Slow work thread pool: Starting up
Slow work thread pool: Ready
[drm] Initialized radeon 2.1.0 20080528 for 0000:01:03.0 on minor 0
Waiting for required block device discovery
Waiting for 1 sda-like device(s)...^ <=====Hang here.
Version-Release number of selected component (if applicable):
kernel-2.6.32.59
kexec-tools-133.el6
How reproducible:
Always
Steps to Reproduce:
1.Install RHEL6 on hp-dl380g6-01.rhts.eng.bos.redhat.com
2.Set up kdump
3.Trigger a crash
Actual results:
System hang
Expected results:
System works fine
Additional info:
I tried both x86_64 and i686 on this machine, they all didn't work. But the console log shows some different.
This is i686:
=========================================
......
Waiting for required block device discovery
Waiting for 1 sda-like device(s)...^
And, this is x86_64:
=========================================
......
Waiting for required block device discovery
Waiting for 1 sda-like device(s)...Uhhuh. NMI received for unknown reason b1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
DRHD: handling fault status reg 2
INTR-REMAP: Request device [[02:00.0] fault index 37
INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear
DRHD: handling fault status reg 102
INTR-REMAP: Request device [[02:00.0] fault index 35
INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear
DRHD: handling fault status reg 202
INTR-REMAP: Request device [[02:00.0] fault index 33
INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear
Comment 5RHEL Program Management
2010-08-10 08:38:33 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 6RHEL Program Management
2010-08-18 21:24:47 UTC
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Red Hat Enterprise Linux. Unfortunately, we
are unable to address this request in the current release. Because we
are in the final stage of Red Hat Enterprise Linux 6 development, only
significant, release-blocking issues involving serious regressions and
data corruption can be considered.
If you believe this issue meets the release blocking criteria as
defined and communicated to you by your Red Hat Support representative,
please ask your representative to file this issue as a blocker for the
current release. Otherwise, ask that it be evaluated for inclusion in
the next minor release of Red Hat Enterprise Linux.
Description of problem: I find kexec-tools doesn't works on hp-dl380g6-01.rhts.eng.bos.redhat.com. ...... Console: switching to colour frame buffer device 128x48 fb0: radeondrmfb frame buffer device drm: registered panic notifier Slow work thread pool: Starting up Slow work thread pool: Ready [drm] Initialized radeon 2.1.0 20080528 for 0000:01:03.0 on minor 0 Waiting for required block device discovery Waiting for 1 sda-like device(s)...^ <=====Hang here. Version-Release number of selected component (if applicable): kernel-2.6.32.59 kexec-tools-133.el6 How reproducible: Always Steps to Reproduce: 1.Install RHEL6 on hp-dl380g6-01.rhts.eng.bos.redhat.com 2.Set up kdump 3.Trigger a crash Actual results: System hang Expected results: System works fine Additional info: I tried both x86_64 and i686 on this machine, they all didn't work. But the console log shows some different. This is i686: ========================================= ...... Waiting for required block device discovery Waiting for 1 sda-like device(s)...^ And, this is x86_64: ========================================= ...... Waiting for required block device discovery Waiting for 1 sda-like device(s)...Uhhuh. NMI received for unknown reason b1 on CPU 0. You have some hardware problem, likely on the PCI bus. Dazed and confused, but trying to continue DRHD: handling fault status reg 2 INTR-REMAP: Request device [[02:00.0] fault index 37 INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear DRHD: handling fault status reg 102 INTR-REMAP: Request device [[02:00.0] fault index 35 INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear DRHD: handling fault status reg 202 INTR-REMAP: Request device [[02:00.0] fault index 33 INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear