-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault in dracut --sysroot due to recursive kernel module installs #2680
Comments
Update: If I omit the
However, if I specify that I want the
|
CC @mwilck and @aafeijoo-suse for SLES |
The problem does not occur if I explicitly chroot into the directory where the OS image is, and then run
It seems that the problem may be related to having to specify the full path to the kernel modules when the
|
We have this soft dependency on (open)SUSE:
The bug that this is supposed to solve is ancient (2014). It's well possible that this softdep isn't necessary any more. But as usual with things like that, it's hard to get rid of them, especially after such a long time, because we can't be sure whether users still rely on it. But it doesn't cause endless recursion on plain SUSE systems. So I suppose this happens if SLE and RHEl are mixed together like in your case. I have no experience with this kind of setup. But as you're essentially building for RHEL, I suppose you should be using the soft dependencies that are valid and tested for RHEL, rather than those of the host system. |
@mwilck Thank you for your response. The recursion does not occur if instead of using the |
Ok, can this be closed then? |
Yes. I thought that |
Describe the bug
A clear and concise description of what the error is.
I am running SLES15SP6 on the host and have a RHEL 8.10 chroot environment for which I would like to create an
initramfs.img
.Run this command:
The debug output shows that there is a recursive loop that leads to a segmentation fault.
Here are the dependencies in the chroot environment. I'm not sure why the debug output shows that the
uas
kernel module is being installed, since theusb-storage
kernel module does not have a dependency on it. It is theuas
kernel module that has a dependency onusb-storage
, but I didn't request for theuas
kernel module to be installed.Distribution used
Which distribution was this behaviour seen in?
SLES15SP6 in the host and RHEL 8.10 in the chroot environment
Dracut version
Which dracut version was this behaviour seen in?
Init system
Which init system is being used?
To Reproduce
Steps or code to reproduce the behavior.
See description of the bug.
Expected behavior
A clear and concise description of what you expected to happen.
No recursive loop and no segmentation fault.
Additional context
Add any other context you like about the problem here.
The text was updated successfully, but these errors were encountered: