Interesting. What makes me wonder is how you're getting SIGSEGV, not SIGILL. In my experience, if the binary contains code that your processor doesn't understand, Linux raises SIGILL, not SIGSEGV, as well it should, because they're very different types of problem.
Can you run a test for me? Make a note of the stuff you see crashing, and then use ldd on them to see what dynamic libraries they share. If it's just glibc, well, then it might be a problem with glibc, or maybe, god forbid, either part of or all of the entire Fedora 28 i686 package set is defective and needs to be rebuilt.
This is concerning. I have some old PIII systems I use myself, but I haven't upgraded them to Fedora 28 yet. Hopefully the problem isn't too massive.
On 2018-05-08 12:48 am, Ralf Corsepius wrote:
seems to me as if f28 has become unusable on non-pae systems.
At least, an attempt to upgrade my PIII from f27 (functional!) to f28 ended up with numerous segfaults, originating from cron, mount.nfs, automount and NetworkManager (and likely more) all similar to this:
...: segfault at bf44bfc4 at b79e35ac sp bf44bfc0 error 6 in libc-2.27.so[b787c000+19000]
I currently don't have any time to investigate any further, but my gut feeling is RHBZ#1482798 might have returned.
X86 mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com