Unnamed repository
9726838241
Resolves: https://issues.redhat.com/browse/RHEL-7028
Currently, nfs dumping fails on some machines that has a dedicated PHY
driver (dealing with the physical layer) or MDIO bus (connecting the MAC
to PHY devices) driver. This is because kexec-tools doesn't install
dedicated PHY or MDIO driver explicitly. Usually a NIC driver shouldn't
specify the dependency on the needed PHY or MDIO driver because it
shouldn't a NIC (medium access control, MAC) driver is for dealing with
the Data link layer and a PHY driver is for physical layer. So as long
as a MAC driver can talk to the PHY layer via APIs, it shouldn't care
which PHY driver or device it's talking to. So when the
dependency on a PHY driver or MDIO driver is not found by dracut's
instmods, the PHY or MDIO driver won't be installed.
This patch passes =drivers/net/phy and =drivers/net/mdio to dracut's
instmods which will only install in-use PHY or MDIO driver(s).
Note ideally we should find out which PHY driver is used by a NIC but
unfortunately currently no universal way can be found
(/sys/class/net/NIC_NAME/phydev/driver/module can be used to find the
name of the PHY driver for some NICs but it doesn't exist for some NICs
like Qualcomm Atheros AR8031). So is it for a MDIO bus driver.
Fortunately currently no huge memory consumption is found for a PHY or
MDIO driver.
Fixes:
|
||
---|---|---|
spec | ||
tests | ||
.editorconfig | ||
.gitignore | ||
.packit.yaml | ||
.shellspec | ||
60-fadump.install | ||
60-kdump.install | ||
92-crashkernel.install | ||
98-kexec.rules | ||
98-kexec.rules.ppc64 | ||
COPYING | ||
crashkernel-howto.txt | ||
dracut-early-kdump-module-setup.sh | ||
dracut-early-kdump.sh | ||
dracut-fadump-init-fadump.sh | ||
dracut-fadump-module-setup.sh | ||
dracut-kdump-capture.service | ||
dracut-kdump-emergency.service | ||
dracut-kdump-emergency.target | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress.sh | ||
early-kdump-howto.txt | ||
fadump-howto.txt | ||
gating.yaml | ||
gen-kdump-conf.sh | ||
gen-kdump-sysconfig.sh | ||
kdump-dep-generator.sh | ||
kdump-in-cluster-environment.txt | ||
kdump-lib-initramfs.sh | ||
kdump-lib.sh | ||
kdump-logger.sh | ||
kdump-migrate-action.sh | ||
kdump-restart.sh | ||
kdump-udev-throttler | ||
kdump.conf.5 | ||
kdump.service | ||
kdumpctl | ||
kdumpctl.8 | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.28-Fix-building-on-x86_64-with-binutils-2.41.patch | ||
kexec-tools-2.0.28-kexec-don-t-use-kexec_file_load-on-XEN.patch | ||
kexec-tools-2.0.28-makedumfpile-0001-PATCH-ppc64-get-vmalloc-start-address-from-vmcoreinf.patch | ||
kexec-tools.spec | ||
live-image-kdump-howto.txt | ||
Makefile | ||
mkdumprd | ||
mkdumprd.8 | ||
mkfadumprd | ||
README | ||
README.packit | ||
sources | ||
supported-kdump-targets.txt | ||
zanata-notes.txt |
Adding a patch to kexec-tools ============================= There is a mailing list kexec@lists.fedoraproject.org where all the dicussion related to fedora kexec-tools happen. All the patches are posted there for inclusion and committed to kexec-tools after review. So if you want your patches to be included in fedora kexec-tools package, post these to kexec@lists.fedoraproject.org. One can subscribe to list and browse through archives here. https://admin.fedoraproject.org/mailman/listinfo/kexec