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:
Due to non-availability of Hyper-V video driver hyperv_fb in kdump
initramfs, the console seems to be in hang state with no text over it.
Version-Release number of selected component (if applicable):
kexec-tools-2.0.15-16.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start os
2. Add "crashkernel=auto" to kernel parameter and reboot
3. Start kdump service and check kdump is running
# kdumpctl status
Kdump is operational
4. Check the kdump initramfs does not include hyperv_fb
# lsinitrd /boot/initramfs-3.10.0-915.el7.x86_64kdump.img | grep hyperv_fb
5. Trigger the crash and check the console
# echo c > /proc/sysrq-trigger
Actual results:
After kernel crash, the console seems to be in hang state with no text
over it until reboot
Expected results:
The logs will be visible over console after crash
Additional info:
If add hyperv_fb in kdump initramfs, the logs will be visible over console
1) Ensure /etc/kdump.conf contains the following line :
extra_modules hyperv_fb
2) Restart kdump service and check the kdump initramfs including the
hyperv_fb module
# lsinitrd /boot/initramfs-3.10.0-915.el7.x86_64kdump.img | grep hyperv_fb
Arguments: --hostonly --hostonly-cmdline --hostonly-i18n -o 'plymouth
dash resume ifcfg' --mount '/dev/mapper/rhel_bootp--73--131--181-root
/sysroot xfs defaults' --add-drivers ' hyperv_fb'
--no-hostonly-default-device -f
-rw-r--r-- 1 root root 6636 Jun 22 20:09
usr/lib/modules/3.10.0-915.el7.x86_64/kernel/drivers/video/hyperv_fb.ko.xz
3) Trigger the crash and check the console, check logs will be visible
over console
# echo c > /proc/sysrq-trigger
Refer to https://access.redhat.com/solutions/3500231 and
https://bugzilla.redhat.com/show_bug.cgi?id=1228774
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:3240