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
[f29 aarch64] segfaults in post scripts #1663
Comments
When I then try Just the relevant |
Hm. Does the system seem to function OK outside of rpm-ostree? I mean, here we have Can you e.g. use |
Both On a second attempt, |
I have no idea whether this is significant or a red herring and I have a few unique pis3s. I tried Version: 29.20181106.0 (2018-11-06T11:14:51Z). The first program failing seems to be eg:
|
Can you attach the output of |
Cross-linking https://bugzilla.redhat.com/show_bug.cgi?id=1648112 |
You should be able to experiment with See
|
|
I'm not clear whether rofiles-fuse is supposed to work like this, but I'm sure that you do, and nothing crashes:
I don't know whether this is relevant, but I did create the error message EDIT by @dustymabe to improve markdown formatting for web viewing. |
I don't know whether this helps or not, but persistence is sometimes a workaround:
ie, the install failed, then worked. The only major difference being the download and import of one package. It may also be worth noting that the whole process seems to spend a lot of time waiting for the SDCard on the pis. |
Maybe we are sensitive somehow to really slow media? Or maybe it's possible the SD card is becoming un-reliable? Might be worth trying on a different one to see if you can reproduce easily. It would at least be a good datapoint. |
I tried that on a new pi 3 from Element 14, which comes with a 16GB class 10 micro SDCard, with I tried After reboot, It may be significant that before the fail error message, there was a message that reached the tty: Would it help to have the symbols for |
I'm also wondering whether there's use of some other HW, like crc HW accel that's causing us issues here but I'm not sure if the fuse things would use kernel crc which might be accelerated. I have seem errors around CRC in some of the output of crashes. We seem to be some how tweaking the HW (for which bit I'm not sure) in some unusual way which we don't see with a non ostree Fedora install. |
I bought a RPi a while ago but never got around to using it...will dig through my stuff to see if I can find it. One thing I notice looking at the OpenSSL source is that
Only thing I can think of related to that is that rpm-ostree calls into grub2-mkconfig which calls os-prober which will definitely end up initializing the kernel crypto API since it probes for RAID which uses checksums. The Use of FUSE by default is definitely something that distinguishes rpm-ostree from yum. We could theoretically use overlayfs (like podman does) when privileged (as rpm-ostree acting on the host is). |
Not that I'm aware of but we do have clevis-luks (and related) installed for TPM2 disk encryption support so I wonder if it tweaks anything in this context.
Yes, that makes sense as I've similar output around crypto API when doing an "rpm-ostree update" as when booting and the system is probing for rootfs. Does moving to BLS here like is planned for F-30 for defaults (and as can be used in F-29) have any impact here and does it change/impact rpm-ostree?
Yes, we also seem to bit hitting this device is some special way that we don't do elsewhere here which is ultimately a bug somewhere so it would be good to get to the bottom of it as it's quite strange, I have a RPi3B+ with a sandisk card that doesn't seem to be hitting it, but I have a RPi3 original which seems to destroy SD cards every few month with vanilla Fedora. |
dunno whether this helps or not - pls stop me posting noise if that's what it is. I tried an upgrade today and got a couple of different failures:
The second of these looked a lot like earlier fails. However, the first one showed a new type of error (to me), which I thought might help identify where things are going awry:
|
So, was reading the libfuse and kernel codebases. This is total conjecture but I have a theory that this might be some kind of race condition between the FUSE kernel module being loaded and
This Again, total conjecture, but thought it might be helpful. This is hard to help debug without being able to reproduce locally. If you always |
Well that worked the first time (one data point). I'll add them as I try more. |
I have the same issue, 100% of the time (tried it about 10 times). Fresh install of IoT on an RPi3. Used to run regular Fedora on it and it worked fine, so I don't think this is a hardware issue. Podman also seems to work fine. Running Edit: A few more attempts and it actually succeeded. So it does not fail 100% of the time, but pretty darn close. |
Host system details
Raspberrypi 3
Provide the output of
rpm-ostree status
.Expected vs actual behavior
Expected:
Steps to reproduce it
Provide any additional data that may help debug this - which specific version of
an RPM is in the repo, or any host system configuration.
The exact errors seem intermittent. Is it just a service availability issue on one of the repos?
Would you like to work on the issue?
Sorry, I'm too far behind the curve on this. Happy to provide more info.
journalctl.txt
The text was updated successfully, but these errors were encountered: